[self-SOLVED]vim + lilypond syntax highlighting

I'm trying to get vim to use syntax highlighting in lilypond files. Apparently lilypond comes with the necessary files, but I have not been able to make vim find them (?). I am not very experienced with vi(m), so there might be something wrong with my setup.
I have, of course, both vim and lilypond installed. The files for lilypond syntax highlighting are in subdirectories of /usr/share/lilypond/2.12.3/vim/. Vim syntax highlighting works for other files, such as C++, HTML, etc., so no problem there. My ~/.vimrc file contains
set runtimepath+=/usr/share/lilypond/2.12.3/vim/
as per instruction given in http://lilypond.org/doc/v2.12/Documenta … m/Vim-mode (and the path is correctly modified). But when I open a lilypond file (with the correct .ly suffix) all I get is black and white. What's the problem?
[EDIT: Oh heck, nevermind! Apparently I was getting too tired to read instructions properly. Was missing the ~/.vim/filetype.vim file described in the above link.]
Last edited by lotuskip (2010-04-12 18:33:42)

You're right about it being overridden. This change should be able to be placed in ~/.vimrc though.
Well that was foolish - I should have read the comments right below in that file. It says exactly how to set it in vimrc. I've now added the following to my ~/.vimrc and this is completely solved without modifying the /usr/... file.
let g:tex_flavor = "tex"
Last edited by Trilby (2013-03-29 16:11:26)

Similar Messages

[SOLVED] VIM: different syntax highlighting for new vs existing file

I've had this minor nagging issue for a while that I've been trying to figure out, but I just don't know where to look.
It is most obvious with LaTeX files (*.tex). When I create a new file with "vim file.tex" it is recognized as a latex file and I get syntax highlighting, but it seems odd, or off. When I close then reopen the same file, it gets "propper" syntax highlighting.
I gather that this must be because of the two different mechanisms for matching the syntax type: filename versus content. When the file is new, vim only uses the extension. Once there is a latex comand (e.g., "\documentclass{article}") it recognizes it as something else and the highlighting style is different.
It turns out just by actually elaborating exactly what the problem was, I was able to find the solution. I looked for how vim recognizes the files, and found two relevant lines in /usr/share/vim/vim73/filetype.vim on lines 2093 and 2094. Apparently the .tex filetype is not the same as .latex and others. I changed it so it was, and I got the desired behavior.
I thought about just not posting this - but it may be useful for others.

You're right about it being overridden. This change should be able to be placed in ~/.vimrc though.
Well that was foolish - I should have read the comments right below in that file. It says exactly how to set it in vimrc. I've now added the following to my ~/.vimrc and this is completely solved without modifying the /usr/... file.
let g:tex_flavor = "tex"
Last edited by Trilby (2013-03-29 16:11:26)

Vim complex syntax highlight

I'm trying to create a vim syntax file for writing. I'm detecting matching quote marks so I change the color of quotes, and I'm also detecting plain text stylings like /italics/ and *bold* to modify the style accordingly. However, I can't seem to combine them.
For example:
black black black "green green green" black black.
black black black *bold-black* black
black black black "green green green *bold-black* green" black.
Is there a way for vim to preserve the color of the containing element but modify the style (or vice versa)?
Thanks.

Hi,
$ echo $TERM
xterm
And
:set ft
filetype=php
:set syntax
syntax=php
Using aterm does work! But is there any option to enable colors under xterm?
thanks
phrakture wrote:
Before you enter vim, what is the output of "echo $TERM".
When inside vim, what is the output ":set ft" and ":set syntax"?

[SOLVED] syntax highlighting in vim

Hi,
How do you guys set syntax highlighting in your vimrc? For example, I have a bunch of mutt config files saved as something like alias.muttrc, colors.muttc, etc... and I want them all to use the muttrc syntax.
Currently, I have this in my vimrc:
au BufNewFile,BufRead *.muttrc setf muttrc
This works unless my first line is a comment (or first non-blank line). Which is annoying because I want to begin with a comment sometimes!
Also, I noticed that if my main config file--muttrc--is set correctly whether or not it begins with a comment. (This file is already matched to muttrc syntax without my intervention).
Does anyone have a better/different way of setting the syntax?
Last edited by miggy (2009-05-27 16:15:44)

Thanks for the suggestion but I'm experiencing the same behavior. Something weird's going on. Can someone confirm this same behavior?
file1.muttrc
color normal white default
file2.muttrc
# Comment
color normal white default
file3.muttrc
color normal white default
# Comment
As I'm writing these, they all are good, but when I go to edit them, only file1.muttrc has the correct highlighting. The others can get it if I say :set syntax=muttrc.
It's especially weird that the comments are highlighted but nothing else is. If I'm not using any sort of file detecting then not even the comments are highlighted

[Solved][VIM] E484: Can't open file syntax.vim

Hi all,
I've installed Archlinux few days ago on my netbook and yesterday i decided to configure Vim using plugins.
During plugins configuration, i messed up and i decided to revome all Vim files in my ~ folder in order to restart configuration.
However, since I've executed the `rm -R .vim .vimrc .viminfo` command, I can't re-activate Vim's syntax coloration using `syntax on` into my .vimrc file nor into Vim directly.
Here is the error message when I start Vim :
Error detected while processing /home/romain/.vimrc:
line 1:
E484: Can't open file /home/romain/.vim/syntax/syntax.vim
Press ENTER or type command to continue
I've found this topic on BBS which seems to be the same problem as me but reinstalling vim or vi doesn't solve this problem.
I've tried to copy this syntax.vim file from /usr/share/vim/vim73/syntax/syntax.vim but it doesn't solve the problem and I want a clean solution without hacking my ~ folder ; moreover, this bug also appears being root while I haven't configured vim with the root account so it may be a problem into Vim's installation folders or something.
Thanks for your help and sorry I my english contains mistakes,
MicroJoe.
Last edited by MicroJoe (2012-06-14 16:16:45)

This is the output :
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 7 2012 00:41:40)
Rustines incluses : 1-547
Compilé par ArchLinux
Grosse version sans interface graphique.
Fonctionnalités incluses (+) ou non (-) :
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs
-dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path
+find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape
+mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse
+mouse_xterm +mouse_urxvt +multi_byte +multi_lang -mzscheme -netbeans_intg
+path_extra +perl +persistent_undo +postscript +printer -profile -python
-python3 +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent
-sniff +startuptime +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
-toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp
-xterm_clipboard -xterm_save
fichier vimrc système : "/etc/vimrc"
fichier vimrc utilisateur : "$HOME/.vimrc"
fichier exrc utilisateur : "$HOME/.exrc"
$VIM par défaut : "/usr/share/vim"
Compilation : gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -march=i686 -mtune=generic -pipe -fstack-protector --param=ssp-buffer-size=4 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Édition de liens : gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -L/usr/local/lib -Wl,--as-needed -o vim -lm -lncurses -lacl -lattr -lgpm -ldl -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -fstack-protector -L/usr/local/lib -L/usr/lib/perl5/core_perl/CORE -lperl -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
(I've noticed that some part were in French but I hope that it'll not be a problem).

Lost syntax highlight in Vim after upgrade

I don't know why, but Vim is not enabling syntax highlight anymore after the upgrade from 7.1.12-1 to 7.1.63-1. I've already searched in Vim's website and with ':help syntax.txt' but no luck. Any guesses?
EDITED:
I figured out part of the problem. I've always used the syntax 'vi filename' to open my files because I knew Vi had a link to Vim. But now it's not linking anymore. Opening files with 'vim filename' gives me the syntax highlight. So I guess the last upgrade had removed the link. Any chances to have it back?
Last edited by alexmatos (2007-08-12 14:07:06)

I had the same problem too, but the difference is, I always use vim, but after upgrading Arch I lost syntax highlight. After googling a lot and lurking @ vim sites I finally found the indirect answer here!
I tried the opposite and use vi to open files but bash said vi not found, I did pacman -S vi, and pac said vi is up to date, upgrade? I decided not to believe vi and upgraded, everything's back now.
So thank you for helping without knowing.

Tweak vims syntax highlighting

here is a little tutorial for making your own s-h theme for vim,
if you're using gvim you can skip the part about terminals,
for terminal users you must first set your prefered terminal colours in .Xdefaults ,
eg for urxvt:
urxvt*scrollColor: #111111
urxvt*font: xft:Bitstream Vera Sans Mono:pixelsize=13
urxvt*scrollBar_floating: false
urxvt*scrollstyle: urxvt
urxvt*saveLines: 1000
urxvt*foreground: #eeeeee
urxvt*background: #000000
! black
urxvt*color0: #000000
urxvt*color8: #444444
! red
urxvt*color1: #b21818
urxvt*color9: #ee9090
! green
urxvt*color2: #18b218
urxvt*color10: #54ee54
! yellow
urxvt*color3: #968a38
urxvt*color11: #eeee77
! blue
urxvt*color4: #1818b2
urxvt*color12: #9090ee
! magenta
urxvt*color5: #963c59
urxvt*color13: #cf9ebe
! cyan
urxvt*color6: #418179
urxvt*color14: #71bebe
! white
urxvt*color7: #aaaaaa
urxvt*color15: #eeeeee
then you save this example file as ~/.vim/colors/xerxes.vim
" local syntax file - set colors on a per-machine basis:
hi clear
set background=dark
if exists("syntax_on")
syntax reset
endif
let g:colors_name = "xerxes"
hi Normal guifg=white guibg=black
hi Scrollbar guifg=darkcyan guibg=cyan
hi Menu guifg=black guibg=cyan
hi SpecialKey term=bold cterm=bold ctermfg=2 guifg=Blue
hi NonText term=bold cterm=bold ctermfg=darkred gui=bold guifg=Blue
hi Directory term=bold cterm=bold ctermfg=brown guifg=Blue
hi ErrorMsg term=standout cterm=bold ctermfg=grey ctermbg=blue guifg=White guibg=Red
hi Search term=reverse ctermfg=white ctermbg=red guifg=white guibg=Red
hi MoreMsg term=bold cterm=bold ctermfg=darkgreen gui=bold guifg=SeaGreen
hi ModeMsg term=bold cterm=bold gui=bold guifg=White guibg=Blue
hi LineNr term=underline cterm=bold ctermfg=darkcyan guifg=Yellow
hi Question term=standout cterm=bold ctermfg=darkgreen gui=bold guifg=Green
hi StatusLine term=bold,reverse cterm=bold ctermfg=4 ctermbg=15 gui=bold guifg=blue guibg=white
hi StatusLineNC term=reverse ctermfg=white ctermbg=lightblue guifg=white guibg=blue
hi Title term=bold cterm=bold ctermfg=darkmagenta gui=bold guifg=Magenta
hi Visual term=reverse cterm=reverse gui=reverse
hi WarningMsg term=standout cterm=bold ctermfg=red guifg=Red
hi Cursor guifg=bg guibg=Green
hi Comment term=bold ctermfg=6 guifg=#80a0ff
hi Constant term=underline ctermfg=9 guifg=#ffa0a0
hi Special term=bold ctermfg=1 guifg=Orange
hi Identifier term=underline ctermfg=14 guifg=#40ffff
hi Statement term=bold cterm=bold ctermfg=11 gui=bold guifg=#ffff60
hi PreProc term=underline ctermfg=5 guifg=#ff80ff
hi Type term=underline cterm=bold ctermfg=lightgreen gui=bold guifg=#60ff60
hi Error term=reverse ctermfg=darkcyan ctermbg=black guifg=Red guibg=Black
hi Todo term=standout ctermfg=black ctermbg=darkcyan guifg=Blue guibg=Yellow
hi link IncSearch Visual
hi link String Constant
hi link Character Constant
hi link Number Constant
hi link Boolean Constant
hi link Float Number
hi link Function Identifier
hi link Conditional Statement
hi link Repeat Statement
hi link Label Statement
hi link Operator Statement
hi link Keyword Statement
hi link Exception Statement
hi link Include PreProc
hi link Define PreProc
hi link Macro PreProc
hi link PreCondit PreProc
hi link StorageClass Type
hi link Structure Type
hi link Typedef Type
hi link Tag Special
hi link SpecialChar Special
hi link Delimiter Special
hi link SpecialComment Special
hi link Debug Special
now you can start tweaking the theme, use the numbers in .Xdefaults as your prefered colours in the "ctermfg" and "ctermbg" commands,
now you can use the "colorscheme" command in vim to enable it,
colorscheme xerxes

hello iphitus,
i've edited the first post and if you use that .Xdefaults the following scheme should give you something close to desert,
" Vim color file
set background=dark
if version > 580
" no guarantees for version 5.8 and below, but this makes it stop
" complaining
hi clear
if exists("syntax_on")
syntax reset
endif
endif
let g:colors_name="desert"
hi Normal guifg=White guibg=grey20
" highlight groups
hi Cursor guibg=khaki guifg=slategrey
"hi CursorIM
"hi Directory
"hi DiffAdd
"hi DiffChange
"hi DiffDelete
"hi DiffText
"hi ErrorMsg
hi VertSplit guibg=#c2bfa5 guifg=grey50 gui=none
hi Folded guibg=grey30 guifg=gold
hi FoldColumn guibg=grey30 guifg=tan
hi IncSearch guifg=slategrey guibg=khaki
"hi LineNr
hi ModeMsg guifg=goldenrod
hi MoreMsg guifg=SeaGreen
hi NonText guifg=LightBlue guibg=grey30
hi Question guifg=springgreen
hi Search guibg=peru guifg=wheat
hi SpecialKey guifg=yellowgreen
hi StatusLine guibg=#c2bfa5 guifg=black gui=none
hi StatusLineNC guibg=#c2bfa5 guifg=grey50 gui=none
hi Title guifg=indianred
hi Visual gui=none guifg=khaki guibg=olivedrab
"hi VisualNOS
hi WarningMsg guifg=salmon
"hi WildMenu
"hi Menu
"hi Scrollbar
"hi Tooltip
" syntax highlighting groups
hi Comment guifg=SkyBlue
hi Constant guifg=#ffa0a0
hi Identifier guifg=palegreen
hi Statement guifg=khaki
hi PreProc guifg=indianred
hi Type guifg=darkkhaki
hi Special guifg=navajowhite
"hi Underlined
hi Ignore guifg=grey40
"hi Error
hi Todo guifg=orangered guibg=yellow2
" color terminal definitions
hi SpecialKey ctermfg=darkgreen
hi NonText cterm=bold ctermfg=darkblue
hi Directory ctermfg=darkcyan
hi ErrorMsg cterm=bold ctermfg=7 ctermbg=1
hi IncSearch cterm=NONE ctermfg=yellow ctermbg=green
hi Search cterm=NONE ctermfg=grey ctermbg=blue
hi MoreMsg ctermfg=darkgreen
hi ModeMsg cterm=NONE ctermfg=brown
hi LineNr ctermfg=3
hi Question ctermfg=green
hi StatusLine cterm=bold,reverse
hi StatusLineNC cterm=reverse
hi VertSplit cterm=reverse
hi Title ctermfg=5
hi Visual cterm=reverse
hi VisualNOS cterm=bold,underline
hi WarningMsg ctermfg=1
hi WildMenu ctermfg=0 ctermbg=3
hi Folded ctermfg=darkgrey ctermbg=NONE
hi FoldColumn ctermfg=darkgrey ctermbg=NONE
hi DiffAdd ctermbg=4
hi DiffChange ctermbg=5
hi DiffDelete cterm=bold ctermfg=4 ctermbg=6
hi DiffText cterm=bold ctermbg=1
hi Comment ctermfg=12
hi Constant ctermfg=9
hi Special ctermfg=5
hi Identifier ctermfg=10
hi Statement cterm=bold ctermfg=11
hi PreProc ctermfg=1
hi Type ctermfg=2
hi Underlined cterm=underline ctermfg=5
hi Ignore cterm=bold ctermfg=7
hi Ignore ctermfg=darkgrey
hi Error cterm=bold ctermfg=7 ctermbg=1

Vim, Perl and syntax highlight

Hello all,
Suppose you have a little snippet of Perl code like such:
sub foo # some comment with keywords for die and or not
print "In sub foo!\n";
The comment in the sub line is not treated (i.e. highlighted) as a comment. Rather, it is highlighted as regular source code. Seems like a bug, but before reporting it to the maintainer, I wanted to see if anyone else shared the same issue.
To clarify: this refers only to highlight in vim, running the code works as expected. And I took care to see if this could be the results of my settings: the problem seems in fact, to be with the perl.vim file (in my system: /usr/share/vim/vim73/syntax/perl.vim).
So, can anyone reproduce this behaviour?

frabjous wrote:Yes, same for me. (I don't write perl, so I don't have anything special installed for it other than the default /usr/share/vim73/syntax/perl.vim.)
Hum, ok. I'll report it to the maintainer then.

[SOLVED] vim color highlighting not correctly displayed in vc/tty

For instance visual selection is set up to change fg/bg to black/green but changes fg to green. Under x using urxvt it displays correctly.
Last edited by Noble (2010-07-26 21:22:19)

I have written my own syntax highlight theme, post below. If you think your script could do anything about it after looking at the file please post But as I said, vim works fine in urxvt, but not when I switch out of X and run it in the vc/tty.
:set statusline=#%n\ %y\ %F\ %r\ %=%c\ %l/%L
:set hlsearch
:set nocompatible
:set noexrc
:set number
:syntax enable
:set autochdir
:set backup
:set backupdir=~/.vim/backup
:set directory=~/.vim/tmp
:set autoindent
:set ruler
:set nowrap
:set nocp
:set scrolloff=5
:set sidescrolloff=5
:set fileformats=unix,dos,mac
:set title
:set laststatus=2
:set tabstop=4
:set autoread
:set showcmd
:set showmatch
:set shiftwidth=4
:set smarttab
:set backspace=indent,eol,start
filetype on
filetype plugin on
filetype indent on
hi clear
set background=dark
if exists("syntax_on")
syntax reset
endif
highlight ErrorMsg ctermfg=red ctermbg=none cterm=bold
highlight WarningMsg ctermfg=red ctermbg=none cterm=bold
highlight VertSplit ctermfg=green ctermbg=black
highlight Folded ctermfg=magenta ctermbg=none
highlight FoldColumn ctermfg=magenta ctermbg=none
highlight FoldColumn ctermfg=magenta
highlight LineNr ctermfg=green cterm=bold
highlight ModeMsg ctermfg=lightgreen cterm=bold
highlight MatchParen ctermfg=black ctermbg=green
highlight Normal ctermfg=white ctermbg=none
highlight SignColumn ctermfg=magenta
highlight NonText ctermfg=blue
highlight Question ctermfg=red cterm=bold
highlight Comment ctermfg=8
highlight Constant ctermfg=green cterm=none
highlight Identifier ctermfg=white cterm=bold
highlight Statement ctermfg=lightgreen cterm=bold
highlight PreProc ctermfg=10
highlight Type ctermfg=2
highlight Special ctermfg=cyan
highlight Error ctermfg=red ctermbg=none
highlight Todo ctermfg=yellow ctermbg=none cterm=bold
highlight StatusLine ctermfg=black ctermbg=green cterm=none
highlight StatusLineNc ctermfg=black ctermbg=lightgreen cterm=none
highlight Directory ctermfg=white
highlight Search ctermfg=black ctermbg=green cterm=none
highlight Visual ctermfg=black ctermbg=lightgreen
highlight WildMenu ctermfg=black ctermbg=cyan cterm=none
highlight Pmenu ctermfg=black ctermbg=green
highlight PmenuSel ctermfg=black ctermbg=lightgreen cterm=none

[SOLVED] Associate extensions to syntax highlights pluma/gedit

Hi,
I am trying to make pluma/gedit use the SQL syntax highlight by default, when I open or create a file
with extension .hql (hive).
I think I added correctly the mime for hql file, but it still doesn't work.
Can you help me with this issue?
(also if there is an hive syntax highlighter for pluma it is even better, but for the moment I would be happy just to highlight it as an Sql file).
Thanks a lot in advance for the help,
Cheers,
Luca
Last edited by lucacerone (2014-12-10 11:50:17)

Hi,
go to:
/usr/share/gtksourceview-3.0/language-specs
edit sql.lang:
sudo gedit sql.lang
go to line 27 and change
<property name="globs">*.sql</property>
to
<property name="globs">*.sql;*.hql</property>
and restart gedit. Worked for me (Ubuntu 14.04 LTS)
Cheers

[SOLVED] `Vim/Gvim: set mouse=a works only in Gvim?

I'm diving into the world of (g)vim this weekend and although I'm starting to get the hang of things, I seem to be having a problem with the mouse functionality. I have set mouse=a specified in my .vimrc and gvim respects it, but when I run vi in a terminal session (urxvt) I have to explicitly type :set mouse=a in ex mode before it will work. Am I missing something?
Here's what I've got in my .vimrc (linked also ~/.gvimrc) so far:
" (G)vim settings
set nocompatible " use gVim defaults
colorscheme wombat " define syntax color scheme
syntax on " enable syntax highlighting
set mouse=a " make sure mouse is used in all cases.
set backspace=2 " full backspacing capabilities
set nocindent " set C style indenting off
set cmdheight=2 " command line height
set ignorecase " ignore case in search patterns
set laststatus=2 " occasions to show status line, 2=always.
set ruler " ruler display in status line
set showmode " show mode at bottom of screen
set number " toggle line numbers
set nobackup " disable backup files (filename~)
set hlsearch " highlight all search results
set showmatch " show matching brackets (),{},[]
" Gvim Settings
set guioptions-=T " disable toolbar icons
set guifont=Consolas\ 8 " backslash any spaces
SOLVED: Silly me I was running 'vi' which has no X support... pacman -S vim fixed it fine.
Last edited by thayer.w (2007-09-04 00:02:49)

I just had an issue with no sound after recent updates. Not sure it's the same problem you are having.
I found I had to open Audio Mixer, select Sound card: HDA Intel PCH (Alsa mixer), Select Controls, check box for Speaker and check box for Headphones. After doing this I found the Speaker volume was set at minimum (although Master and PCM were already set at maximum). Adjusted Speaker volume up and I finally had sound again.

Enable syntax highlighting with configuration file in emacs

When editing configuration files such as .procmailrc, .fetchmailrc, Emacs won't automatically highlight syntax for me.
I can enable syntax highlighting in Vim by appending "syntax on" to the .vimrc.
I tried adding "global-font-lock-mode t" in the .emacs file, but it didn't solve my problem.
What is the solution?

igndenok wrote:
Some of my config file have this (using conf-unix-mode)
# this is .somerc
# -*- conf-unix -*-
Or using this in your .emacs
(add-to-list 'auto-mode-alist '("\\.*rc$" . conf-unix-mode))
I followed your advice, and it does have some syntax highlighting, but less than Vim does.
For example, Vim will highlight all the names of colors in the .muttrc file, but Emacs doesn't.
I guess Emacs is not as strong as Vim when it comes to editing configuration files.
Last edited by yu3k (2011-09-14 10:06:47)

HTML editor with syntax highlighting and UTF-8 support

In an ongoing effort to move our lives into the cloud and into our pockets (and as a part of an article series for a tech blog), me and a friend are trying to completely replace the need for computers with our iPhones.
In some ways, it is going splendidly (Documents to Go Premium + foldable bluetooth keyboard = all my writing needs as a journalist solved). In others, concessions have to be made (as a practicing musician, my options are a bit limited, but with the help of Xewton Music Studio, Multitrack DAW/NanoStudio, etc, I can at least lay down some basic tracks, create basic MIDI compositions, etc).
However, there is one area in where we’ve made no headway at all. My friend has the great misfortune of being blessed with logic , and therefore, unlike me, does honest programming and web app designing work. And as far as we know, there is not a single HTML/script editor with more than just the bare, basic functions in the app store.
What we need is this:
* Syntax highlighting
* Support for UTF-8
A built-in FTP editor would be a nice bonus, but is not essential.
We found one for the iPad, but when we contacted the company behind the app, they revealed no immediate plans for an iPhone version. (They felt coding on the iPhone was, at best, impractical, but they did concede the fact that if there are indeed users who have that need, the existence of an iOS HTML editor would be justified, and possible lucrative, regardless of their feelings on the matter. On that ground, they promised to examine the possibilities to port their iPad app in the future, but so far, no signs.)
Does anyone know of such an app? Rest assured your assistance will be mentioned in the article series should you point us in the right direction

Unfortunately, my friend has offered his iPhone an ultimatum. No syntax highlighting, no computer replacement. It is strange that such as standardized feature has not found its way into any known HTML editor for iOS.
But FTPOntheGo seems to be a great app in general, so thanks!

Syntax Highlighting for MATRIXx MathScript and TPL

There have been some questions about text editors for MATRIXx, so I wanted to let everyone know about an application note that we just posted. It describes how to configure a syntax highlighter for use with MathScript and Template Programming Language (TPL). There is also an example of how Crimson Editor can be configured. I choose Crimson Editor because it was free, but the same thing can be done in other syntax highlighters. Using a syntax highlighter makes MATRIXx code a lot easier to read.
http://zone.ni.com/devzone/conceptd.nsf/webmain/C43375149CB01C3186256E530081EAA5
While I am at it, I am going to point out some other resources. The application note is located on Developer Zone section of our website, where
you can find other MATRIXx examples and tutorials:
http://zone.ni.com/devzone/devzone.nsf/webcategories/A92DB8BA2DE149F486256CBC00655A0C?opendocument
If you have code or examples that you want to share with other users you can submit the example to the Example Code Library:
http://www.ni.com/devzone/dev_exchange/ex_search.htm
Suggestions and feedback can be submitted from Product Feedback section of Contact NI:
http://sine.ni.com/apps/we/nicc.call_me?p_action=country&p_lang_id=US
And of course the main MATRIXx page is:
http://www.ni.com/matrixx
Carl L
National Instruments

I found another editor with syntax highlighting capabilities for MATRIXx. The editor is VIM which is based on the Unix VI editor, and is available on both Solaris and Windows.
www.vim.org
Carl L
National Instruments
www.ni.com/matrixx

[Solved] Vim: Can only undo most recent change

Howdy-ha, folks. So I've been (very) gradually making the transition from Geany to Vim over several months, mostly without issue. However, I've been reluctant to use Vim for anything other than quick, simple operations for one reason: The "u" key will only undo the most recent change, as though there aren't any other changes in the history. Hitting "u" a second time reverses the "undo" command, so that repeatedly hitting it will just remove and add the same small change over and over again. No matter how much time I spend looking into this it seems I'm the only person who's ever had this problem, and it occurs regardless of whether /etc/vimrc and ~/.vimrc exist. As a result, I can't do any complex editing for fear of botching something and needing to spend hours backtracing my mistakes. Any help on this is appreciated.
Last edited by ANOKNUSA (2012-05-18 15:22:06)

skanky wrote:It should do. There's a comment in /etc/vimrc recommending against changing, so it's worth looking into. There are other settings there that could affect some behaviour, apparently.
That would likely be the issue: I overwrote the default with my own config file, without including runtime! archlinux.vim in my own config. As far as I can tell, things are working as both user and root. I suppose I should have paid more attention, but then again, there's no mention in the Arch wiki entry about not altering/deleting any of those files:
Arch Wiki Vim Entry wrote:
Vim's personal configuration file is located in the home directory: ~/.vimrc. Advanced users tend to keep a well-tailored ~/.vimrc. The global configuration file is located at /etc/vimrc. The fall-back $VIM variable is defined as /usr/share/vim/. For example, to create a global colorscheme the *.vim colorscheme file should be stored in /usr/share/vim/vimfiles/.
Currently, the vim global configuration in Arch Linux is very basic and differs from many other distributions' default vim configuration file. To get some commonly expected behaviors (like syntax highlighting, return to the line of the last edit...), consider using vim's example configuration file:
cp /etc/vimrc /etc/vimrc.bak
cp /usr/share/vim/vim73/vimrc_example.vim /etc/vimrc
It seems the comment in /usr/share/vim/vimfiles/archlinux.vim is all new users have to go on, and it's not usually the first place anyone looks.

[self-SOLVED]vim + lilypond syntax highlighting

Similar Messages

Maybe you are looking for