Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #225413 > unrolled thread

midnight commander editor

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  midnight commander editor mick crane <mick.crane@gmail.com> - 2020-07-28 12:10 +0200
    Re: midnight commander editor Reco <recoverym4n@enotuniq.net> - 2020-07-28 12:50 +0200
      Re: midnight commander editor Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-28 13:50 +0200
        Re: midnight commander editor mick crane <mick.crane@gmail.com> - 2020-07-28 17:20 +0200

#225413 — midnight commander editor

hello,
using mc to select files to edit mc editor doesn't recognize vim syntax 
colouring so have to press enter to ignore and get the error messages in 
terminal.
Any way to have mc recognize colo, syntax options in ~/.vimrc ?

mick
-- 
Key ID    4BFEBB31

[toc] | [next] | [standalone]

#225414

	Hi.

On Tue, Jul 28, 2020 at 11:00:30AM +0100, mick crane wrote:
> hello,
> using mc to select files to edit mc editor doesn't recognize vim syntax colouring so have to press enter to ignore and get the error messages in terminal.
> Any way to have mc recognize colo, syntax options in ~/.vimrc ?

mcedit(1), chapter SYNTAX HIGHLIGHTING:

wholechars abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ_

# default colors
define  comment   brown
context default
  keyword  whole  if       yellow
  keyword  whole  else     yellow
  keyword  whole  for      yellow
  keyword  whole  while    yellow
  keyword  whole  do       yellow
  keyword  whole  switch   yellow
  keyword  whole  case     yellow
  keyword  whole  static   yellow
  keyword  whole  extern   yellow
  keyword         {        brightcyan
  keyword         }        brightcyan
  keyword         '*'      green


Does it have anything in common with a typical syntax/*vim file?

syn match   plsqlKeyword "\<END\>"
syn match   plsqlKeyword "\.COUNT\>"hs=s+1
syn match   plsqlKeyword "\.EXISTS\>"hs=s+1
syn match   plsqlKeyword "\.FIRST\>"hs=s+1
syn match   plsqlKeyword "\.LAST\>"hs=s+1
syn match   plsqlKeyword "\.DELETE\>"hs=s+1
syn match   plsqlKeyword "\.PREV\>"hs=s+1
syn match   plsqlKeyword "\.NEXT\>"hs=s+1


There is no way of doing what you want, syntax highlighting is radically
different in mcedit and vim.

Reco

[toc] | [prev] | [next] | [standalone]

#225417

[Multipart message — attachments visible in raw view] — view raw

On Ma, 28 iul 20, 13:42:07, Reco wrote:
> 	Hi.
> 
> On Tue, Jul 28, 2020 at 11:00:30AM +0100, mick crane wrote:
> > hello,
> > using mc to select files to edit mc editor doesn't recognize vim 
> > syntax colouring so have to press enter to ignore and get the error 
> > messages in terminal.
> > Any way to have mc recognize colo, syntax options in ~/.vimrc ?

[...]

> There is no way of doing what you want, syntax highlighting is radically
> different in mcedit and vim.

What can be done though is to set 'vim' as the default editor for mc.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#225423

On 2020-07-28 12:39, Andrei POPESCU wrote:
> On Ma, 28 iul 20, 13:42:07, Reco wrote:
>> 	Hi.
>> 
>> On Tue, Jul 28, 2020 at 11:00:30AM +0100, mick crane wrote:
>> > hello,
>> > using mc to select files to edit mc editor doesn't recognize vim
>> > syntax colouring so have to press enter to ignore and get the error
>> > messages in terminal.
>> > Any way to have mc recognize colo, syntax options in ~/.vimrc ?
> 
> [...]
> 
>> There is no way of doing what you want, syntax highlighting is 
>> radically
>> different in mcedit and vim.
> 
> What can be done though is to set 'vim' as the default editor for mc.

Ahhh!

cheers
mick

-- 
Key ID    4BFEBB31

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web