Re: using hidden unlisted buffer as transparently as possible
* A.J.Mechelynck [EMAIL PROTECTED] [060723 22:23]: Bram: 'exe silent command' apparently does not give the same result as ':silent exe command' (see example below). Bug or feature? gvim -N -u NONE :version VIM - Vi IMproved 7.0 (2006 May 7, compiled Jul 23 2006 22:50:51) Included patches: 1-42 Compiled by [EMAIL PROTECTED] Huge version with GTK2-GNOME GUI. Features included (+) or not (-): [...] Conclusion: It's :silent exe blahblah, not :exe 'silent' blahblah. Note that about half a screen below :help :silent there is an example with :silent exe normal. I see no difference between :silent exe blahblah and :exe silent blahblah. But I did determine the trigger; see below. BTW, I did recompile with patches 1-42 after my last message; the later patches did not appear to have any effect on my problem. Note: While doing those tests, I found that if the current buffer is modified, the function will give an error at line 2. You may want to add let save_hidden = hidden set hidden at the start of the function, and let hidden = save_hidden Thanks, I'll add that (I think; see below). I have 'set hidden' in my .vimrc, but this is a script for public consumption, so I don't want to rely on my own settings! before returning. OTOH I don't quite understand why you must search an auxiliary buffer rather than the current one being edited. Best regards, Tony. The cause of the problem is :set hidden. I tried gvim -N -u NONE and did not see the problem, so I tried gvim (with my normal .vimrc and the rest of the system-wide configuration) and did see the problem. My first thought was autocmds, so I started deleting blocks of autocmds. But, even after deleting all autocmds I still had the problem. A more careful examination of the list from ':set' showed hidden as one of the differences. When I tried gvim -N -u NONE, then :set hidden, the problem returned. Note that once you :set hidden, the problem remains until you not only :set nohidden, but also switch buffers at least once. Bram, is this intentional (or more importantly, can it be changed so that the message is displayed in the right order or at least obeys ':silent')? Tony, thanks very much for your help! ...Marvin
Re: using hidden unlisted buffer as transparently as possible
* Yakov Lerner [EMAIL PROTECTED] [060724 05:27]: 'silent!' in front of (exec b . bufnr) works, no ? The following :args a b :silent! 'exec b 2' :silent! 'exec b 1' :echomsg AAA works for me. Output from 'b #' commands is suppresses, only AAA is printd. Yakov This doesn't work with :set hidden. See my response to Tony for the longer explanation. I do appreciate all of you who regularly contribute suggestions and solutions. I've learned a lot from watching this list. Thanks...Marvin
foldmethod=expr very slow
I use foldmethod=expr with the following foldexpr:
set foldexpr=GetFoldLevel(v:lnum)
function! GetFoldLevel(line)
let line_text = getline(a:line)
if (line_text =~ '\%({.*}\)\|\%(}.*{\)')
return '='
elseif (line_text =~ '{')
return a1
elseif (line_text =~ '}')
return s1
endif
return '='
endfunction
What I want to do is similar to foldmethod=marker with foldmarker={,},
but if I use foldmethod=marker vim gets confused by lines that contain
both { and } like these:
string s = String.Format({0}, v);
string[] sa = new string[] { a, b };
GetFoldLevel() above fixes that, in that it keeps the same fold level
if both { and } are found on the same line, but it is horribly slow.
Even in pretty small files (1k lines long), it can take several
seconds for characters to appear when I'm typing in insert mode.
Is there a way to optimize the above, or an alternative way of doing
this? It is very frustrating to have my folds get out of whack with
foldmethod=marker, but the slowness of this foldexpr is unbearable.
--
Be seeing you.
Re: foldmethod=expr very slow
On Mon, Jul 24, 2006 at 12:30:07PM -0500, Thore B. Karlsen wrote:
I use foldmethod=expr with the following foldexpr:
set foldexpr=GetFoldLevel(v:lnum)
function! GetFoldLevel(line)
let line_text = getline(a:line)
if (line_text =~ '\%({.*}\)\|\%(}.*{\)')
return '='
elseif (line_text =~ '{')
return a1
elseif (line_text =~ '}')
return s1
endif
return '='
endfunction
I haven't read the above too carefully: But if all you want to do is
fold your code based on {...} blocks, then use Vim 7 and set fdm=syntax
(for C / C++ files).
Incidentally, fdm=syntax is also slow (though much much faster than
fdm=expr). I could (grudgingly) live with a short delay when first
loading the file. The thing that bothers me is that when I switch
between buffers, Vim takes it's own sweet time to get the syntax based
folding right.
So I only enable syntax folding for files that have less than 3000
lines. Once my clever spies steal Benji Fisher's computer, I'm going to
up this limit to 18000.
GI
--
You're not drunk if you can lie on the floor without holding on.
Re: foldmethod=expr very slow
On Mon, 24 Jul 2006 13:06:47 -0500, Gautam Iyer
[EMAIL PROTECTED] wrote:
I use foldmethod=expr with the following foldexpr:
set foldexpr=GetFoldLevel(v:lnum)
function! GetFoldLevel(line)
let line_text = getline(a:line)
if (line_text =~ '\%({.*}\)\|\%(}.*{\)')
return '='
elseif (line_text =~ '{')
return a1
elseif (line_text =~ '}')
return s1
endif
return '='
endfunction
I haven't read the above too carefully: But if all you want to do is
fold your code based on {...} blocks, then use Vim 7 and set fdm=syntax
(for C / C++ files).
Unfortunately, that doesn't work for the way I do my folding. I also
insert braces manually in comments where I want folds, e.g.:
//@{ Private data.
private int blah;
//@}
Incidentally, fdm=syntax is also slow (though much much faster than
fdm=expr). I could (grudgingly) live with a short delay when first
loading the file. The thing that bothers me is that when I switch
between buffers, Vim takes it's own sweet time to get the syntax based
folding right.
I wonder why, because you'd think it would be about the same work as
just figuring out the syntax highlighting?
So I only enable syntax folding for files that have less than 3000
lines. Once my clever spies steal Benji Fisher's computer, I'm going to
up this limit to 18000.
I have a quad qore Opteron machine, perhaps if vim could take
advantage of all the CPUs it would be tolerable. :)
--
Be seeing you.
findfile() results are inconsistent
Hello, Results of findfile() are inconsistent: /home/mikolaj/a /home/mikolaj/1/b /home/mikolaj/2/c /home/mikolaj/3/d /home/mikolaj/3/4/e 1. We are in /home/mikolaj:: echo findifile(b, 1;) 1/b 2. We are in /home/mikolaj/2:: echo findifile(b, /home/mikolaj/1;) /home/mikolaj/1/b 3. We are in /home/mikolaj/3/4:: echo findifile(d, /home/mikolaj/3/4;) /home/mikolaj/3/d Why this inconsistence? Also mention of ; as obligatory element would be good addition to docs. m.
Re: findfile() results are inconsistent
Results of findfile() are inconsistent: The results seem consistent to me. /home/mikolaj/a /home/mikolaj/1/b /home/mikolaj/2/c /home/mikolaj/3/d /home/mikolaj/3/4/e 1. We are in /home/mikolaj:: echo findifile(b, 1;) 1/b You are giving findfile() a relative path to search, so it is returning a relative result. 2. We are in /home/mikolaj/2:: echo findifile(b, /home/mikolaj/1;) /home/mikolaj/1/b You are giving findfile() an absolute path to seach, so it is returning an absolute result. 3. We are in /home/mikolaj/3/4:: echo findifile(d, /home/mikolaj/3/4;) /home/mikolaj/3/d Once again you supply an absolute path, so it returns an absolute result. If you need to expand a relative result to its absolute path or strip off portions of an absolute result, you can always use fnamemodify(). -- eric
Re: foldmethod=expr very slow
Hi Thore,
I've never tried folding like this before, and unfortunately I don't have time
to try out this 'optimized' version, but it may work faster for you (I've just
replaced the regex matches with stridx and rearranged the code flow):
set foldexpr=GetFoldLevel()
function! GetFoldLevel()
let line_text = getline(v:lnum)
let left_idx = (stridx(line_text, '{') = 0)
let right_idx = (stridx(line_text, '}') = 0)
if left_idx
if ! right_idx
return 'a1'
endif
elseif right_idx
return 's1'
endif
return '='
endfunction
HTH,
Peter
--- Thore B. Karlsen [EMAIL PROTECTED] wrote:
I use foldmethod=expr with the following foldexpr:
set foldexpr=GetFoldLevel(v:lnum)
function! GetFoldLevel(line)
let line_text = getline(a:line)
if (line_text =~ '\%({.*}\)\|\%(}.*{\)')
return '='
elseif (line_text =~ '{')
return a1
elseif (line_text =~ '}')
return s1
endif
return '='
endfunction
What I want to do is similar to foldmethod=marker with foldmarker={,},
but if I use foldmethod=marker vim gets confused by lines that contain
both { and } like these:
string s = String.Format({0}, v);
string[] sa = new string[] { a, b };
GetFoldLevel() above fixes that, in that it keeps the same fold level
if both { and } are found on the same line, but it is horribly slow.
Even in pretty small files (1k lines long), it can take several
seconds for characters to appear when I'm typing in insert mode.
Is there a way to optimize the above, or an alternative way of doing
this? It is very frustrating to have my folds get out of whack with
foldmethod=marker, but the slowness of this foldexpr is unbearable.
--
Be seeing you.
Send instant messages to your online friends http://au.messenger.yahoo.com
Re: findfile() results are inconsistent
Mikolaj Machowski wrote: Hello, Results of findfile() are inconsistent: /home/mikolaj/a /home/mikolaj/1/b /home/mikolaj/2/c /home/mikolaj/3/d /home/mikolaj/3/4/e 1. We are in /home/mikolaj:: echo findifile(b, 1;) 1/b 2. We are in /home/mikolaj/2:: echo findifile(b, /home/mikolaj/1;) /home/mikolaj/1/b 3. We are in /home/mikolaj/3/4:: echo findifile(d, /home/mikolaj/3/4;) /home/mikolaj/3/d Why this inconsistence? Also mention of ; as obligatory element would be good addition to docs. m. I don't see any inconsistency. According to the help, findfile() is Just like |finddir()|, but find a file instead of a directory. and finddir() has: When the found directory is below the current directory a relative path is returned. Otherwise a full path is returned. Isn't that what you got? Is the semicolon really obligatory? :lcd $VIMRUNTIME/doc :echo findfile(help.txt,.) (without a colon), returns help.txt, which is the expected result.
Re: Other European languages on a US keyboard
On Mon, Jul 24, 2006 at 03:36:54AM EDT, Matthew Winn wrote: On Sun, Jul 23, 2006 at 06:41:09PM -0400, cga2000 wrote: Avoid words such as coeur.. boeuf.. etc. Rather amazing that the French who are so picky about anything that concerns their language never came up with a codepage.. or whatever it's called that features this particular character. I think it dates from the days when typewriters were popular. The US dominance of the market for office equipment prompted many European languages to manage without combinations like oe, ae and ij where the characters can be approximated by typing separate letters. It's easier to change typing habits than to manufacture a new range of typewriters just to deal with one special letter. .. hmm.. as far as I know only France and Germany went to the trouble of designing their own typewriter keyboard layouts separate from the QWERTY model. I think Polish keyboards are derived from the German layout.. I would assume variations of the French layout are used in other French-speaking countries and some African countries.. As to other European countries - ie. the ones that speak neither French nor German - I believe that you are correct and that they use derivatives of the US keyboard. Therefore, since the French went so far as building keyboards that have the basic letters arranged differently (AZERTY instead of QWERTY) it would not have been such a major enhancement to provide an oe some place on that keyboard..? I have a feeling it is more a question of whoever designed the original French typewriter keyboard just did not think it worth bothering with such typographic niceties as providing an o dans l'e (or is it the other way round?) when the end result with fixed-width characters was going to be light-years removed from the refinements of traditional typesetting anyway.. But I would agree that the absence of the oe on French keyboards (typewriters and computers alike) probably accounts for the fact that you can't find it anywhere in the latin* charsets. Prior to computers many keyboards didn't even have separate keys for the digits 1 and 0, typists using the letters l and O instead. I was aware of the l/1 thing.. sometimes use it when I feel lazy. Thanks cga
global normal command with yanking
Hi, I want to assemble a line below a block of text, where the fist word of every line is concatenated. one bla two bla three bla four bla empty line So I tried this, which should for every line yank the first word, Go to the last (empty) line, pastes and appends a little text after. :1,$-g/^/normal yeGPa + The result is: four + three + two + one + The order is not how I expected it. Why is that, and can I reverse the order? Thank You Joachim ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/
Re: global normal command with yanking
On 7/24/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I want to assemble a line below a block of text, where the fist word of every line is concatenated. one bla two bla three bla four bla empty line So I tried this, which should for every line yank the first word, Go to the last (empty) line, pastes and appends a little text after. :1,$-g/^/normal yeGPa + The result is: four + three + two + one + The order is not how I expected it. :1,$-g/^/normal yeG$pa + Yakov
Re: Other European languages on a US keyboard
As you say, warning: off-topic post. Read at your own risk. This discussion underlines all the more strongly why I don't attempt to produce final documents using vim: I sometimes use an actual word processor like Open Office Writer, but mostly I write in HTML and, of course, the best HTML editor on the planet is... ...vim! Russ P.S. Yes, typing eacute; , oelig; and uuml; is painful, but I'm one of those perfectionists who would have used half-spacing back in the old days if I had been in need of such things. My father used a non-electric typewriter, but I was 19 before I moved to France from the US and needed what wasn't on the keyboard. After coming back at 25 (some 26+ years ago now), I never lost the need to communicate and product documents of with accents, digraphs, etc. in fact, I added the need to compose classical Greek texts while in France, but that's a whole other mess. A.J.Mechelynck wrote: Warning: off-topic post. Read at your own risk. Before computers, I used a French typewriter keyboard (AZERTY type). Nowadays I use a Belgian computer keyboard (also AZERTY but with special characters arranged differently). My father has an old typewriter he bought in Switzerland when he was a student, and it uses a QWERTZ layout. (Switzerland has four official languages, viz. German, French, Italian and Romanche; and I don't know how many different keyboards they use.) On a mechanical typewriter, it was possible to use half-spacing by holding the space bar down. So, if one wanted to produce the oe digraph on a French typewriter (not an electric one though), it was possible -- for a perfectionist. Let's say I wanted to type boeuf (= beef/ox): 1. press and hold spacebar. This advances the carriage by one half space 2. hit b. This prints b without moving the carriage. 3. release, press and hold spacebar. 4. hit o 5. release spacebar. The carriage is now over the right half of the o. 6. hit e u f in succession. The oe digraph is called o, e dans l'o and the ae digraph is called in French a, e dans l'a. The latter as in Serge Gainsbourg's song elaeudanla téitéia (which spells the name Laetitia). French typewriters indeed seldom had the digits one and zero: small-ell and big-oh were used insted. But it even carried over to computers: Several decades ago (before the merger with Honeywell), the (French) Bull computer company used on its computers a charset where the same character could mean either zero or O-for-Oscar depending on context -- and another one, I think, could mean one or I-for-India. (Few computers had lowercase in those days.) This, of course, caused headaches without end when trying to convert those computers' magnetic tapes to IBM's BCD and EBCDIC standards or to (whose? PDP? CDC? other?) ASCII. I'm not sure non-English non-French non-German speaking countries all use a US-derived keyboard, even if we limit ourselves to those that use variants of the Latin alphabet. Typewriters, after all, date back to (I think) before World War I, a time when English was much less dominant internationally than it is now. At the courts of St-Petersburg and Potsdam, French was spoken; Germany and Austria together covered (or had recently covered) a territory that went from Alsace to Silesia and from Schleswig-Holstein to the plain of the Po. I suspect that most of Central Europe would have adopted a German-derived (or maybe French-derived) keyboard regardless of whether the majority language was Czech, Slovak, Italian, Hungarian, Croatian... I agree that the lack of oe OE digraphs in the Latin charsets is probably due to their absence on French typewriter keyboards. (AE ae were kept because they are used in Danish.) There is more than a single-letter difference with English though: not only the layout is different but there are several accented letters. The French (and Belgian) keyboards have a dead key for circumflex and trema/diaeresis/umlaut, but à ç é è ù and sometimes uppercase-C-cedilla each have their own glyphs. (In French, uppercase letters with the exception of C-cedilla and sometimes E-acute were usually left unaccented. I believe computers are slowly pushing back the trend.) Best regards, Tony.
Re: Other European languages on a US keyboard
Russell Bateman wrote: As you say, warning: off-topic post. Read at your own risk. This discussion underlines all the more strongly why I don't attempt to produce final documents using vim: I sometimes use an actual word processor like Open Office Writer, but mostly I write in HTML and, of course, the best HTML editor on the planet is... ...vim! ;-) Russ P.S. Yes, typing eacute; , oelig; and uuml; is painful, but I'm one of those perfectionists who would have used half-spacing back in the old days if I had been in need of such things. My father used a non-electric typewriter, but I was 19 before I moved to France from the US and needed what wasn't on the keyboard. After coming back at 25 (some 26+ years ago now), I never lost the need to communicate and product documents of with accents, digraphs, etc. in fact, I added the need to compose classical Greek texts while in France, but that's a whole other mess. ... and I bought an IBM ball typewriter so I could type not only Latin but also Greek and Russian. I even lent it to the World Esperanto Congress of 1982 in Antwerp, so journalists could write home in their respective languages. Don't know if they used it (the keyboard layout must have felt weird to them). Somewhere at vim-online I have a script htmlmap.vim which auto-converts ç to ccedil; É to Eacute; etc. as you type; and F12 o e to #339; etc. (not all browsers understand oelig; -- or did when I started: Netscape 4, e.g., didn't). (Useful when the browser doesn't know if it's reading UTF-8 or some flavour of Latin.) Source it from %HOME%\vimfiles\after\ftplugin\html.vim or ~/.vim/after/plugin/html.vim. I'm not sure if it works when 'encoding' is set to UTF-8 though. Best regards, Tony.
RE: Other European languages on a US keyboard
Rare enough .. but besides oeuf is also occurs in such very common words as voeu [wish] and coeur [heart] and it really bothers me when I see them incorrectly spelled in web pages for instance. I spot it and after that I tend to lose focus and not be able to take in what I'm reading for a short while. How're they misspelled? Or, if none of the distributed keymaps is exactly what you want, you can write your own. It isn't hard. See :help :loadkeymap for the theory, and look at the contents of Bram's $VIMRUNTIME/keymap/accents.vim and my $VIMRUNTIME/keymap/esperanto_utf8.vim for a couple of simple examples. Already started on this: copied accents.vim to ~/.vim/keymap/ .. renamed it to foreign.vim and added the Spanish inverted question / exclamation marks - an for now I have mapped to !! and ??. Come to think of it, French would appear to have the most annoying spelling system of the West European languages that I have some degree of familiarity with. Spanish, Italian, and German seem to use fewer non-ASCII characters. In order to set up my foreign language keymap correctly I would really need tables of all the characters that occur in these languages, decide which ones are common enough to be worth adding to the keymap, and make sure I build a scheme that's coherent before I get my fingers to memorize it. I'll scour the Wiki's later today.. see if I can find anything useful. If you wouldn't mind, definitely keep me in the loop on this one, as I've got something of an interest. Offhand, some contributions and questions: beta-looking SS (German) slashed 'l' (Polish) slashed 'o' (Scandinavian or thereabouts, not sure if Dutch or other) AElig/aelig/OElig/oelig (Latin, etc.) ccedil/Ccedil (how done, ,C?) ecedil(?) (also Polish, possibly other vowels, 'though don't recall offhand) Oh, someone on the list is native Polish, so might ask him. Was it Mikolaj? Dunno anyone Dutch who'd recall the slashed-'o'. How to enter Aring (eg, Aring;ngstrom)? oA?? Synonymous with aa (eg, Haas == Haring;s?) Oh, well...
Problem starting up vim: No mapping found
Hi, fellow vimmers, just returning to work after two weeks, I found that vim on several Linux machines doesn't start up properly anymore; it says Keine Zuordnung gefunden Keine Zuordnung gefunden (twice the same message; after removing the LANG environment variable, the english version No mapping found was used) On most systems I can continue after the prompt Hit ENTER or type command to continue, but on one just nothing happens, and I'm not able to edit the given file. Maybe I did anything very stupid two weeks ago, but I'm quite sure I did nothing worse than maybe adding a file to the ftplugin directory; the error occurs regardless of the edited file type. When calling vim as ex, the error occurs /after/ editing the file. My vim version (SuSE Linux 9.1): VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Apr 6 2004 03:03:03) Included patches: 1-8, 10-12, 14-18, 20-21, 25-32, 34-35, 37, 40, 43-46, 48-55, 58-59, 61-65, 67-89, 91-98, 100-102, 104-106, 108-114, 117, 119-120, 122, 126, 129, 133, 135-137, 139, 143-155, 157-160, 162-172, 174-176, 178, 180-187, 189-193, 195-198, 200-204, 206-209, 213, 216-224, 228-229, 231-232, 234, 237-242, 244-251, 253-263 Compiled by [EMAIL PROTECTED] Big version without GUI. Features included (+) or not (-): +arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +dialog_con +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -netbeans_intg -osfiletype +path_extra -perl +postscript +printer -python +quickfix +rightleft -ruby +scrollbind +signs +smartindent -sniff +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 system vimrc file: /etc/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /etc f-b for $VIMRUNTIME: /usr/share/vim/current Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -Wall -Wall -pipe -fno-stric t-aliasing Linking: gcc -L/usr/local/lib -o vim -lncurses -lselinux -lacl -ldl The vimrc file is the standard SuSE version with the single addition set background=dark; I could post it if desired (2kB when gzipped). Any ideas what might have gone wrong, or how I could figure out /which/ mapping could not be found, would be warmly appreciated... Thanks in advance! -- Tobias
Re: Problem starting up vim: No mapping found
On 7/24/06, Tobias Herp [EMAIL PROTECTED] wrote: Hi, fellow vimmers, just returning to work after two weeks, I found that vim on several Linux machines doesn't start up properly anymore; it says Keine Zuordnung gefunden Keine Zuordnung gefunden (twice the same message; after removing the LANG environment variable, the english version No mapping found was used) On most systems I can continue after the prompt Hit ENTER or type command to continue, but on one just nothing happens, and I'm not able to edit the given file. Maybe I did anything very stupid two weeks ago, but I'm quite sure I did nothing worse than maybe adding a file to the ftplugin directory; the error occurs regardless of the edited file type. When calling vim as ex, the error occurs /after/ editing the file. My vim version (SuSE Linux 9.1): VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Apr 6 2004 03:03:03) Included patches: 1-8, 10-12, 14-18, 20-21, 25-32, 34-35, 37, 40, 43-46, 48-55, 58-59, 61-65, 67-89, 91-98, 100-102, 104-106, 108-114, 117, 119-120, 122, 126, 129, 133, 135-137, 139, 143-155, 157-160, 162-172, 174-176, 178, 180-187, 189-193, 195-198, 200-204, 206-209, 213, 216-224, 228-229, 231-232, 234, 237-242, 244-251, 253-263 Compiled by [EMAIL PROTECTED] Big version without GUI. Features included (+) or not (-): +arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent -clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +dialog_con +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse -mouseshape +mouse_dec -mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -netbeans_intg -osfiletype +path_extra -perl +postscript +printer -python +quickfix +rightleft -ruby +scrollbind +signs +smartindent -sniff +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 -xfontse t -xim -xsmp -xterm_clipboard -xterm_save system vimrc file: /etc/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc fall-back for $VIM: /etc f-b for $VIMRUNTIME: /usr/share/vim/current Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -Wall -Wall -pipe -fno-stric t-aliasing Linking: gcc -L/usr/local/lib -o vim -lncurses -lselinux -lacl -ldl The vimrc file is the standard SuSE version with the single addition set background=dark; I could post it if desired (2kB when gzipped). Any ideas what might have gone wrong, or how I could figure out /which/ mapping could not be found, would be warmly appreciated... You can find from where this message comes using % vim -V20 or % vim -V20 21 | tee logfile and examiging logfile later. In the logfile, you will see the line number and script name. Ignore the Vim: Warning: Output is not to a terminal in later case. BTW, the message No mapping found comes from command :map with lhs but empty rhs, like :map xyz. Yakov
Re: Other European languages on a US keyboard
cga2000 wrote: I sometimes need to write text in other languages such as French, Spanish and occasionally German or Italian. ..snip.. I would like to do this in Vim. Unfortunately I only have a US keyboard. Have you considered EasyAccents.vim? http://vim.sourceforge.net/scripts/script.php?script_id=451 It doesn't use the spelling checker in vim 7.0, but it accepts a' a` a^ a: etc to generate accented characters. Easy to turn on and off, too: \eza toggles. Regards, Chip Campbell
Re: Other European languages on a US keyboard
Schleswig-Holstein to the plain of the Po. I suspect that most of Central Europe would have adopted a German-derived (or maybe French-derived) keyboard regardless of whether the majority language was Czech, Slovak, Italian, Hungarian, Croatian... In fact Polish traditional keyboard is modelled after German layout (with addition of Polish diacritics on separate keys). Only very fast spreading of computers in the beginning of '90 connected with lack of production of those keyboards lead to wide adoption of Polish programmer keyboard (US 101 with diacritics by AltGr not separate keys). m.
Re: Other European languages on a US keyboard
On Mon, Jul 24, 2006 at 10:50:33AM EDT, Gene Kwiecinski wrote: Rare enough .. but besides oeuf is also occurs in such very common words as voeu [wish] and coeur [heart] and it really bothers me when I see them incorrectly spelled in web pages for instance. I spot it and after that I tend to lose focus and not be able to take in what I'm reading for a short while. How're they misspelled? well .. can't give you a sample of the correct spelling - ie. the single oe character instead of the o .. a space and the e.. - since I am not running with an UTF8 locale.. and even that might not work if you are running latin1 for instance. so to get my meaning you need to go to www.wordreference.com .. enter egg in the Enter Word field and check the English to French radio button.. Enter .. and a few lines down you should see a bunch of oeuf correctly spelled .. bad egg - oeuf pourri, for example.. provided your browser is set up to display UTF8, naturally.. otherwise.. I'll have to put up a screenshot some place.. [...] In order to set up my foreign language keymap correctly I would really need tables of all the characters that occur in these languages, decide which ones are common enough to be worth adding to the keymap, and make sure I build a scheme that's coherent before I get my fingers to memorize it. I'll scour the Wiki's later today.. see if I can find anything useful. If you wouldn't mind, definitely keep me in the loop on this one, as I've got something of an interest. Not much joy where finding tables of all characters used in typesetting for different languages, I'm afraid. I did find this regarding keyboard layouts though: http://www-306.ibm.com/software/globalization/topics/keyboards/registry_index.jsp .. as usual I had a very simplified vision of the problem. Offhand, some contributions and questions: beta-looking SS (German) .. used to know this as an s-tset (phonetic rendering..) slashed 'l' (Polish) no knowledge of slavonic languages here.. sorry. looks like Poland has somewhat switched to a US-derived keyboard where computers are concerned. And Tony was right assuming that most central European countries - Czech.. Slovak.. Slovenian/Croatian.. Moldovan.. Hungarian.. even Rumanian have keyboards that are derived from the German layout. slashed 'o' (Scandinavian or thereabouts, not sure if Dutch or other) don't think Dutch has this. AElig/aelig/OElig/oelig (Latin, etc.) Danes Norwegians have a key for AElig right on the keyboard. ccedil/Ccedil (how done, ,C?) Some keyboards - French.. Italian.. Portuguese.. have a ccedil key ecedil(?) (also Polish, possibly other vowels, 'though don't recall offhand) Doesn't appear to be one on the Polish keyboard as pictured at the IBM site. Oh, someone on the list is native Polish, so might ask him. Was it Mikolaj? Dunno anyone Dutch who'd recall the slashed-'o'. Can't think a town in Holland that has this .. so I would assume it's not indigenous (?) How to enter Aring (eg, Aring;ngstrom)? oA?? Synonymous with aa (eg, Haas == Haring;s?) Oh, well... Yes, I could say I agree with that last remark.. Vast subject.. but quite fascinating.. :-) Real glad I started this thread.. Learned some useful stuff here.. Thanks cga
Re: Other European languages on a US keyboard
Warning: this email is in UTF-8. U+ below (where is in hex) is the Unicode notation for a character (Unicode codepoint) given by value. Gene Kwiecinski wrote: Rare enough .. but besides oeuf is also occurs in such very common words as voeu [wish] and coeur [heart] and it really bothers me when I see them incorrectly spelled in web pages for instance. I spot it and after that I tend to lose focus and not be able to take in what I'm reading for a short while. How're they misspelled? the above should all have œ (oe digraph, as one character) not o followed by e (two characters) Or, if none of the distributed keymaps is exactly what you want, you can write your own. It isn't hard. See :help :loadkeymap for the theory, and look at the contents of Bram's $VIMRUNTIME/keymap/accents.vim and my $VIMRUNTIME/keymap/esperanto_utf8.vim for a couple of simple examples. Already started on this: copied accents.vim to ~/.vim/keymap/ .. renamed it to foreign.vim and added the Spanish inverted question / exclamation marks - an for now I have mapped to !! and ??. Come to think of it, French would appear to have the most annoying spelling system of the West European languages that I have some degree of familiarity with. Spanish, Italian, and German seem to use fewer non-ASCII characters. Spanish and Italian both can accent any vowel (grave accent in Italian, acute accent in Italian), and Spanish also has inverted ? and ! Catalan has some grave-accented vowels, some acute-accented ones, some which can take either, the c-cedilla, and also a lettergroup which I've seen in no other language: ll with a dot at mid-height between them, to mean geminated l (pron. as French ll) as opposed to palatalized l (pron. more or less as Spanish ll). ŀl, U+0140 U+006C, decimal 320 108; K l . followed by plain l. Examples: geminated in coŀlinear, palatalized in coll (mountain pass). The Spanish inverted ? and ! are optional in Catalan but can be used in the middle of a sentence to mark the start of the question or exclamation. The uppercase equivalent (ĿL, used only in full-capitals titles since the geminated ells must be part of different syllables, has Ŀ = U+013F, dec. 319, Ctrl-K L . In order to set up my foreign language keymap correctly I would really need tables of all the characters that occur in these languages, decide which ones are common enough to be worth adding to the keymap, and make sure I build a scheme that's coherent before I get my fingers to memorize it. I'll scour the Wiki's later today.. see if I can find anything useful. If you wouldn't mind, definitely keep me in the loop on this one, as I've got something of an interest. Offhand, some contributions and questions: beta-looking SS (German) ß eszet, U+00DF, decimal 223. Don't know if the accents keymap has it. With digraphs: Ctrl-K s s slashed 'l' (Polish) ł -- don't know the name; I'd guess hard l (pronounced more or less as w in Polish but etymologically related to what the Russian pronounce like the ll in English bell). Don't think accents has it as it is 255. U+0142, decimal 322, Ctrl-K l / -- Uppercase: Ł U+0141, dec. 321, Ctrl-K L / slashed 'o' (Scandinavian or thereabouts, not sure if Dutch or other) Danish and Norwegian, not Swedish, equivalent of German/Swedish ö. ø, U+00F8, decimal 248, Ctrl-K o / -- Uppercase: Ø, U+00D8, decimal 216, Ctrl-K O / -- I guess /O and /o with the accents keymap. In other languages, a similar or identical glyph is used to mean diameter. AElig/aelig/OElig/oelig (Latin, etc.) Among modern languages: Danish Æ AE U+00C6 dec.198 Ctrl-K A E æ ae U+00E6 dec.230 Ctrl-K a e French Œ OE U+0152 dec.338 Ctrl-K O E œ oe U+0153 dec.339 Ctrl-K o e ccedil/Ccedil (how done, ,C?) in the accents keymap, Ithink so. With digraphs, Ctrl-K c , or Ctrl-K C , -- U+00C7, decimal 199 (Ç) and U+00E7, decimal 231 (ç). ecedil(?) (also Polish, possibly other vowels, 'though don't recall offhand) ę, it's not a cedilla, (it's turned the other way), it's called an ogonek (thus: e-ogonek). If your keymap hasn't got it, it's Ctrl-K e ; -- U+0119, decimal 281. Oh, someone on the list is native Polish, so might ask him. Was it Mikolaj? Dunno anyone Dutch who'd recall the slashed-'o'. Its not Dutch, its Danish and Norwegian. Dutch only has ij IJ (usually typed as two letters, it's up to the browser to fetch the presentation form if deemed appropriate, like with French fi ffi fl ffl etc. IJ is used e.g. in IJsland (Iceland), IJszee (the Glacial Ocean, usually the Artic, but there is also a Zuidelijke IJszee around the Antartic continent), IJ (a river in the Netherlands, with the town of IJmuiden at its mouth IIRC), IJssel (two other rivers: Hollandse IJssel and Gelderse IJssel; the latter ends up in the IJsselmeer); ijs (ice) becomes IJs at the start of a sentence, etc. Dutch also has some accented vowels in
Re: Other European languages on a US keyboard
On Mon, Jul 24, 2006 at 09:02:34AM EDT, Russell Bateman wrote: As you say, warning: off-topic post. Read at your own risk. .. don't see this as OT.. Being lazy I skipped the .. in Vim in the subject.. This discussion underlines all the more strongly why I don't attempt to produce final documents using vim: I sometimes use an actual word processor like Open Office Writer, but mostly I write in HTML and, of course, the best HTML editor on the planet is... Maybe I should dump LaTeX and use HTML.. I printed some of the TeX-gen'd stuff and it just looks too beautiful.. I end up with correspondence that looks more like pages torn out of an expensive book.. ...vim! agreed.. natch'.. Russ P.S. Yes, typing eacute; , oelig; and uuml; is painful, but I'm one of those perfectionists who would have used half-spacing back in the old days if I had been in need of such things. My father used a non-electric typewriter, but I was 19 before I moved to France from the US and needed what wasn't on the keyboard. After coming back at 25 (some 26+ years ago now), I never lost the need to communicate and product documents of with accents, digraphs, etc. yes.. have a feeling only the folks at the Académie Française and enlightened foreigners are really concerned about this these days.. I'm sure the French don't take notice or give a damn whether you write laetitia or lætitia.. Hope you get my accents.. cedillas.. and e dans l'a above.. in fact, I added the need to compose classical Greek texts while in France, but that's a whole other mess. [..] Thanks cga
Re: Problem starting up vim: No mapping found
Tobias Herp wrote: My vim version (SuSE Linux 9.1): VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Apr 6 2004 03:03:03) Included patches: 1-8, 10-12, 14-18, 20-21, 25-32, 34-35, 37, 40, 43-46, 48-55, 58-59, 61-65, 67-89, 91-98, 100-102, 104-106, 108-114, 117, 119-120, 122, 126, 129, 133, 135-137, 139, 143-155, 157-160, 162-172, 174-176, 178, 180-187, 189-193, 195-198, 200-204, 206-209, 213, 216-224, 228-229, 231-232, 234, 237-242, 244-251, 253-263 Compiled by [EMAIL PROTECTED] Yakov gave you good advice; here's some more: build vim 7.0 . Also, since you'd indicated that you may have added something to your plugin/ftplugin directory, do a ls -tl in those two directories and find out what the most recent inclusions are. Temporarily remove it/them and see if your message disappears with them. Regards, Chip Campbell
using syntax match two time in one line? fst blocks snd?
background: I want to highlight columns in a table differently (database output) So 1 and 2 will be substituted by either \t or |. = syntax file == hi def link Color1 Macro hi def link Color2 Error Show colors of Color1, Color2 syn keyword Color1 A syn keyword Color2 B syn match Color1 '^1\zs[^1]*\ze' syn match Color2 '^1[^1]*1\zs[^1]*\ze' syn match Color2 '^2[^2]*2\zs[^2]*\ze' = testfile = A B 1aa1bb 2cc2dd explanation lines testfile: Line 1 testline to show Color1 Line 2 testfile to show Color2 Line 3 Here aa and bb should be highlighted with Color1, Color2 ( bb isn't) Line 4 only dd should be highlighted to show that the match pattern works (only difference is 2 instead of 1) Marc
Re: Mac OS 10.3 - v7.0 - netrwPlugin.vim
Vim List wrote: I have not upgraded for some time, so today I did. I read a thread here about the new way the split vertical file explorer and the netrwPlugin.vim plugin. I also got used to the way the old directory and file list would open a file when clicked in the main window. The latest netrw (v102) supports leftmouse and rightmouse to edit/delete(with confirmation request), respectively. Chip Campbell
Re: Other European languages on a US keyboard
On Mon, Jul 24, 2006 at 08:37:47AM EDT, A.J.Mechelynck wrote: Warning: off-topic post. Read at your own risk. [..] Before computers, I used a French typewriter keyboard (AZERTY type). Nowadays I use a Belgian computer keyboard (also AZERTY but with special characters arranged differently). My father has an old typewriter he bought in Switzerland when he was a student, and it uses a QWERTZ layout. (Switzerland has four official languages, viz. German, French, Italian and Romanche; and I don't know how many different keyboards they use.) On a mechanical typewriter, it was possible to use half-spacing by holding the space bar down. So, if one wanted to produce the oe digraph on a French typewriter (not an electric one though), it was possible -- for a perfectionist. Let's say I wanted to type boeuf (= beef/ox): 1. press and hold spacebar. This advances the carriage by one half space 2. hit b. This prints b without moving the carriage. 3. release, press and hold spacebar. 4. hit o 5. release spacebar. The carriage is now over the right half of the o. 6. hit e u f in succession. .. makes my mouth water.. I should try Ebay .. see if I can find an affordable high-end typewriter that does such fancy stuff. The oe digraph is called o, e dans l'o and the ae digraph is called in French a, e dans l'a. The latter as in Serge Gainsbourg's song elaeudanla téitéia (which spells the name Laetitia). phew.. this one took me a couple of minutes to figure out.. !! French typewriters indeed seldom had the digits one and zero: small-ell and big-oh were used insted. But it even carried over to computers: Several decades ago (before the merger with Honeywell), the (French) Bull computer company used on its computers a charset where the same character could mean either zero or O-for-Oscar depending on context -- and another one, I think, could mean one or I-for-India. (Few computers had lowercase in those days.) This, of course, caused headaches without end when trying to convert those computers' magnetic tapes to IBM's BCD and EBCDIC standards or to (whose? PDP? CDC? other?) ASCII. Hehe.. maybe a bit of OT at one point in the designers' career wouldn't have hurt.. Sounds like the year 2000 business.. but worse.. What did they do? Hired a few thousand data entry folks to do the conversion.. Not sure regex's had been invented at the time. .. anyway .. as I always say we should all go back to writing in Latin Roman numerals.. I'm not sure non-English non-French non-German speaking countries all use a US-derived keyboard, even if we limit ourselves to those that use variants of the Latin alphabet. Typewriters, after all, date back to (I think) before World War I, a time when English was much less dominant internationally than it is now. At the courts of St-Petersburg and Potsdam, French was spoken; Germany and Austria together covered (or had recently covered) a territory that went from Alsace to Silesia and from Schleswig-Holstein to the plain of the Po. I suspect that most of Central Europe would have adopted a German-derived (or maybe French-derived) keyboard regardless of whether the majority language was Czech, Slovak, Italian, Hungarian, Croatian... quick googling for keyboard layout shows that you are correct. I don't trust Wiki's 100% but this page has some useful keyboard layouts: http://en.wikipedia.org/wiki/Keyboard_layout I agree that the lack of oe OE digraphs in the Latin charsets is probably due to their absence on French typewriter keyboards. (AE ae were kept because they are used in Danish.) There is more than a single-letter difference with English though: not only the layout is different but there are several accented letters. The French (and Belgian) .. somewhat to my surprise the Belgian keyboard uses the AZERTY layout while the Netherlands use QWERTY. But then this would make sense since as far as I recall Dutch/Flemish is pretty limited to the ASCII charset and that's obviously available on AZERTY keyboards. So they only needed to accomodate the French-speaking community. But doesn't Belgium also have a German-speaking community? Ah.. maybe it was just that most businesses were owned by French-speaking Belgians at the time the layout was adopted.. keyboards have a dead key for circumflex and trema/diaeresis/umlaut, but à ç é è ù and sometimes uppercase-C-cedilla each have their own glyphs. (In French, uppercase letters with the exception of C-cedilla and sometimes E-acute were usually left unaccented. I believe computers are slowly pushing back the trend.) Actually I found that there is such a thing as a US International Keyboard and maybe I could acquire one of those since it all the fancy characters that I would want.. Best regards, Tony. Thanks much for all this pre-computer days lore..! Doesn't hurt to know a little something about where we came from.. Thanks cga
Re: using syntax match two time in one line? fst blocks snd?
On 7/24/06, Marc Weber [EMAIL PROTECTED] wrote: background: I want to highlight columns in a table differently (database output) So 1 and 2 will be substituted by either \t or |. = syntax file == hi def link Color1 Macro hi def link Color2 Error Show colors of Color1, Color2 syn keyword Color1 A syn keyword Color2 B syn match Color1 '^1\zs[^1]*\ze' syn match Color2 '^1[^1]*1\zs[^1]*\ze' syn match Color2 '^2[^2]*2\zs[^2]*\ze' = testfile = A B 1aa1bb 2cc2dd You don't need \ze at the end of match. Besides that, you're trying to do overlapping matches. This requires either contains=..., or nextgroup=. Here's solution using nextgroup=. Somehow, use of \zs screws the coloring. Without \zs, the following works: hi def link Color1 Macro hi def link Color2 Error hi def link Color3 Error syn match Color2 '^2[^2]*2\zs[^2]*' syn match Color1 '^1[^1]*' nextgroup=Color3 syn match Color3 '1[^1]*' contained 1aa1bb 2cc2dd If you add \zs to Color1 and Color3 you'll that it stops working. I dont know why. Yakov
Re: Other European languages on a US keyboard
Of course, we all realize that the original difference between AZERTY and QWERTY was the analyzed solutions to the problem of the likelihood of two typewriter hammers striking the platen in close enough succession that they would jam together and get stuck. Accents arose as a distinction only because the French decided, based presumably on a letter frequency analysis that AZERTY was the optimal key arrangement based on letter frequency in French words while Americans (I've never noticed what they type on in England) chose QWERTY. It was always a puzzle to me in my childhood as to why the keys weren't arranged in a more obvious fashion. It wasn't answered until, as I was acquainted with the Dvorak key layout, it was explained to me why typewriter keys had been arranged like that in the first place. Of course, now, it's all just tradition--strong enough that the Dvorak guys haven't carried the day and the chording guys are just a lone voice in the wilderness. cga2000 wrote: On Mon, Jul 24, 2006 at 08:37:47AM EDT, A.J.Mechelynck wrote: Warning: off-topic post. Read at your own risk. [..] Before computers, I used a French typewriter keyboard (AZERTY type). Nowadays I use a Belgian computer keyboard (also AZERTY but with special characters arranged differently). My father has an old typewriter he bought in Switzerland when he was a student, and it uses a QWERTZ layout. (Switzerland has four official languages, viz. German, French, Italian and Romanche; and I don't know how many different keyboards they use.) [snip]
please, comment my script
Hello! I have to sort python's list quite often, so i want to make a script to do that for example i have: a = [ 'aaa' , 'XXX', '','dsgrg', 'sdgsfdg', 'gfdgffg', 'dfgfdgw:swf', 'sdfsdg', 'sdfgsdg', 'sdgsg', 'sdgsfdg' , 'sdgdsg' ] and i need: a = [ 'aaa', 'dfgfdgw:swf', 'dsgrg', 'gfdgffg', 'sdfgsdg', 'sdfsdg', 'sdgdsg', 'sdgsfdg', 'sdgsfdg', 'sdgsg', '', 'XXX' ] left margin = 2 tab, textwidth=80, sorted case insensitive i wrote script with cut-and-paste method, so i guess it can be optimized and now it works only in vim7, but i think it can be written in vim6 compatible mode, right? script: === func! StrICmp(str1, str2) if (a:str1 ? a:str2) return -1 elseif (a:str1 ? a:str2) return 1 else return 0 endif endfunction let s:cmpref = function( 'StrICmp' ) fun! PySort() let ai_revert = 0 let tw_revert = 0 let ignorecase_revert = 0 if ! autoindent let ai_revert = 1 set autoindent endif if textwidth == 0 let tw_revert = 1 set textwidth=80 endif normal! gvay let text = matchstr(@a, '\s*\zs.*\ze\s*') let list = split(text, '\_s*,\_s*') call sort(list, s:cmpref) let @a = join(list, ', ') normal! gvap normal! normal! normal! gqq if ai_revert set noautoindent endif if tw_revert set textwidth=0 endif endfun map C-S :call PySort()CR === Please, comment! -- Pavel
RE: Other European languages on a US keyboard [OT]
This thread reminded me of an experiment I saw a couple of years ago that really interested me, given my background in AI. http://www.visi.com/~pmk/evolved.html To summarize, a guy is trying to evolve a good keyboard layout by deriving interesting metrics. A use for genetic algorithms at last! Regrettably, he didn't have much luck, with the Dvorak layout winning out against all his genetically created layouts, which implies that either his heuristics weren't strong enough, or he didn't let it evolve for long enough. When I have the time I intend to attempt his experiment myself to see if I can produce any useful results. Max -Original Message- From: Russell Bateman [mailto:[EMAIL PROTECTED] Sent: Monday, July 24, 2006 1:26 PM To: vim@vim.org Subject: Re: Other European languages on a US keyboard Of course, we all realize that the original difference between AZERTY and QWERTY was the analyzed solutions to the problem of the likelihood of two typewriter hammers striking the platen in close enough succession that they would jam together and get stuck. Accents arose as a distinction only because the French decided, based presumably on a letter frequency analysis that AZERTY was the optimal key arrangement based on letter frequency in French words while Americans (I've never noticed what they type on in England) chose QWERTY. It was always a puzzle to me in my childhood as to why the keys weren't arranged in a more obvious fashion. It wasn't answered until, as I was acquainted with the Dvorak key layout, it was explained to me why typewriter keys had been arranged like that in the first place. Of course, now, it's all just tradition--strong enough that the Dvorak guys haven't carried the day and the chording guys are just a lone voice in the wilderness. cga2000 wrote: On Mon, Jul 24, 2006 at 08:37:47AM EDT, A.J.Mechelynck wrote: Warning: off-topic post. Read at your own risk. [..] Before computers, I used a French typewriter keyboard (AZERTY type). Nowadays I use a Belgian computer keyboard (also AZERTY but with special characters arranged differently). My father has an old typewriter he bought in Switzerland when he was a student, and it uses a QWERTZ layout. (Switzerland has four official languages, viz. German, French, Italian and Romanche; and I don't know how many different keyboards they use.) [snip]
I lost gvim on a Debian/testing
Hi, I am an user of gvim on a Debian/testing. I mistakenly deleted some vim, gvim related directories like /etc/vim, /etc/gvim. After that, I was unable to run gvim. Whenever I run it , I always get the vim without gui. I tried reinstall vim-gnome by giving a command apt-get install --reinstall vim-gnome on a console. But no success. It still runs the vim without gui. and I also did: apt-get remove --purge vim-gnome vim-gtk apt-get install vim-gtk dpkg-reconfigure vim-gtk I tried vim-gtk and other variants but no success again. When I look inside the directory /usr/bin I see that the vim.gtk and vim.gnome is already there without any symbolic link. When I run them inside that directory, It still runs vim without gui. It is most likely that I deleted some files related to vim as mentioned above. I think the apt-get was confused after that. The only choice left is to compile it from the source. Goodbye to apt-get for gvim. Can somebody help to me? Without gvim, I feel myself as an orphan. Thanks, Ahmet __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: I lost gvim on a Debian/testing
* http://www.debian.org/doc/FAQ/ch-pkgtools.en.html Check out the part about the `dpkg --purge foo` command. I've found that this is the only command on Debian that truly uninstalls a package. HTH! Tom Purl Hi, I am an user of gvim on a Debian/testing. I mistakenly deleted some vim, gvim related directories like /etc/vim, /etc/gvim. After that, I was unable to run gvim. Whenever I run it , I always get the vim without gui. I tried reinstall vim-gnome by giving a command apt-get install --reinstall vim-gnome on a console. But no success. It still runs the vim without gui. and I also did: apt-get remove --purge vim-gnome vim-gtk apt-get install vim-gtk dpkg-reconfigure vim-gtk I tried vim-gtk and other variants but no success again. When I look inside the directory /usr/bin I see that the vim.gtk and vim.gnome is already there without any symbolic link. When I run them inside that directory, It still runs vim without gui. It is most likely that I deleted some files related to vim as mentioned above. I think the apt-get was confused after that. The only choice left is to compile it from the source. Goodbye to apt-get for gvim. Can somebody help to me? Without gvim, I feel myself as an orphan. Thanks, Ahmet __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Other European languages on a US keyboard
On Mon, Jul 24, 2006 at 12:05:02PM EDT, Charles E Campbell Jr wrote: cga2000 wrote: I sometimes need to write text in other languages such as French, Spanish and occasionally German or Italian. ..snip.. I would like to do this in Vim. Unfortunately I only have a US keyboard. Have you considered EasyAccents.vim? http://vim.sourceforge.net/scripts/script.php?script_id=451 That's exactly the sort of thing I initially had in mind but since I've already spent some time getting familiar with the standard (?) Vim solution (:set keymap=) and it's a breeze to customize I'll probably stick with that. What I like abut the :set keymap solution is that if you wait a fraction of a second between ' and e for instance Vim realizes that you want an apostrophe followed by an e.. not an e with acute accent and moves the cusor to the next position.. Another way to achieve this is to map two apostrophes to the (single) apostrophe in your keymap description.. so you type two ''s in quick succession when you want an apostrophe rather than an accented letter.. But I find the former method more natural. Thanks all the same. Appreciate your help. It doesn't use the spelling checker in vim 7.0, but it accepts a' a` a^ a: etc to generate accented characters. Easy to turn on and off, too: \eza toggles. For some bizarre reason .. something in my Vim setup .. I've never managed to get this '\' leader escape character to work. So for the vimspell plugin for instance I have to type the :* commands. Regards, Chip Campbell
Re: Other European languages on a US keyboard
cga2000 wrote: On Mon, Jul 24, 2006 at 08:37:47AM EDT, A.J.Mechelynck wrote: Warning: off-topic post. Read at your own risk. [...] On a mechanical typewriter, it was possible to use half-spacing by holding the space bar down. So, if one wanted to produce the oe digraph on a French typewriter (not an electric one though), it was possible -- for a perfectionist. Let's say I wanted to type boeuf (= beef/ox): 1. press and hold spacebar. This advances the carriage by one half space 2. hit b. This prints b without moving the carriage. 3. release, press and hold spacebar. 4. hit o 5. release spacebar. The carriage is now over the right half of the o. 6. hit e u f in succession. .. makes my mouth water.. I should try Ebay .. see if I can find an affordable high-end typewriter that does such fancy stuff. You might have to buy an antique: only mechanical (not electrical) typewriters behaved this way. [...] .. somewhat to my surprise the Belgian keyboard uses the AZERTY layout while the Netherlands use QWERTY. But then this would make sense since as far as I recall Dutch/Flemish is pretty limited to the ASCII charset and that's obviously available on AZERTY keyboards. So they only needed to accomodate the French-speaking community. But doesn't Belgium also have a German-speaking community? Ah.. maybe it was just that most businesses were owned by French-speaking Belgians at the time the layout was adopted.. German, or German together with French, is spoken in parts of three cantons (i.e., in part of the territory of three Justices of the Peace), near the German border. The Brussels area is bilingual French/Dutch; a number of municipalities near the French/Dutch language border have, at least in theory, a protected minority of the opposite linguistic persuasion. Said border runs approximately East-West from somewhere between Dunkirk and Lille to the vicinity of Maastricht where it hits the German language area. In the 19th century, the Belgian high classes (nobility, liberal professions, rich merchants, etc.) spoke French as their mother language all over the country. In 1830 (15 years after the merger) the Catholic Belgians revolted against the Calvinist Dutch, then (after rejecting several other candidates) accepted as king Leopold of Saxony-Coburg, a Protestant who was the uncle of Queen Victoria, and married to a daughter of Louis-Philippe Premier, roi des Français (or did he marry her for the occasion?). Louis-Philippe's dynasty was ended for good after only 18 years but Leopold's has endured (with some ups and downs) to this day. The Flemish nationalistic movement was not necessarily created, but at least sponsored by the Germans during both world wars as a possible use of the Divide et impera maxim. The Dutch language has gained equality with French over the Kingdom in general and a quasi-monopole north of the language border, but there is still a strong feeling of resentment against the French-speaking oppressor among part of the Flemish. The far-right racist and nationalistic Vlaams Belang (formerly Vlaams Blok) party has, IIRC, some 20% of the votes in the harbour city of Antwerp... especially in rich boroughs where hardly any Muslim, Jew or French-speaker have ever been sighted... But I digress. keyboards have a dead key for circumflex and trema/diaeresis/umlaut, but à ç é è ù and sometimes uppercase-C-cedilla each have their own glyphs. (In French, uppercase letters with the exception of C-cedilla and sometimes E-acute were usually left unaccented. I believe computers are slowly pushing back the trend.) Actually I found that there is such a thing as a US International Keyboard and maybe I could acquire one of those since it all the fancy characters that I would want.. Oh, golly! Good to know. Hope you won't get stuck with a keyboard that your OS doesn't recognise. Best regards, Tony. Thanks much for all this pre-computer days lore..! Doesn't hurt to know a little something about where we came from.. Thanks cga My pleasure. Best regards, Tony.
Re: Other European languages on a US keyboard
Russell Bateman wrote: Of course, we all realize that the original difference between AZERTY and QWERTY was the analyzed solutions to the problem of the likelihood of two typewriter hammers striking the platen in close enough succession that they would jam together and get stuck. Accents arose as a distinction only because the French decided, based presumably on a letter frequency analysis that AZERTY was the optimal key arrangement based on letter frequency in French words while Americans (I've never noticed what they type on in England) chose QWERTY. It was always a puzzle to me in my childhood as to why the keys weren't arranged in a more obvious fashion. It wasn't answered until, as I was acquainted with the Dvorak key layout, it was explained to me why typewriter keys had been arranged like that in the first place. Of course, now, it's all just tradition--strong enough that the Dvorak guys haven't carried the day and the chording guys are just a lone voice in the wilderness. I don't follow what you're saying about accents (typo?). The French have used accented letters since (IIUC) before Gutenberg invented printing. Yes, the various typewriter keyboards are supposed to be the result of some ergology research, but I don't know the details. IIRC the QWERTY keyboard was invented in England at a time when that was the leading industrial country in the world. W is quite rare in French while -ez is part of the universal second-person-plural ending of verbs; but wouldn't the latter make one think that placing z next to e (well, next on the keyboard, and separated by only S 3 X in the machinery) would cause _more_ jamming in mechanical typewriters? The q is safely away from the u... Best regards, Tony.
Re: Other European languages on a US keyboard
* A.J.Mechelynck on Saturday, July 22, 2006 at 22:40:45 +0200:
The French oe (o, e-dans-l'o) is not defined in the Latin1 encoding,
neither in capitals (as for titles or if the word oeuf [egg] is the
first of a sentence), nor in lowercase. You need UTF-8 for it,
No. Just latin9 or ISO8859-15 (Look at the header of this mail).
Mon cœur.
This is on a Mac with a German keyboard, but using actually an
American keyboard layout. I enter the œ with Alt-q (the Alt
key on Mac keyboard corresponds to the Modifier key on other
keyboards I believe).
$ echo $LANG
en_US.ISO8859-15
Alain Bench @ mutt-users pointed me to this site:
http://www.in-ulm.de/~mascheck/locale/
where you can get also a little utility at
http://www.in-ulm.de/~mascheck/locale/checklocale.c
It gives the following output here:
[Latin1/9] If there's no real copyrightsymbol at the end of this sentence,
then your terminal/terminalemulator/font is not ISO8859-1/15 ready: ©
- Current environment settings:
LANG= en_US.ISO8859-15
- Implicitly setting all locale categories with LANG succeeded.
Testing LC_CTYPE with isprint():
# # # # # # # # # # # # # # # #
# # # # # # # # # # # # # # # #
! # $ % ' ( ) * + , - . /
0 1 2 3 4 5 6 7 8 9 : ; = ?
@ A B C D E F G H I J K L M N O
P Q R S T U V W X Y Z [ \ ] ^ _
` a b c d e f g h i j k l m n o
p q r s t u v w x y z { | } ~ #
# # # # # # # # # # # # # # # #
# # # # # # # # # # # # # # # #
¡ ¢ £ € ¥ Š § š © ª « ¬ ® ¯
° ± ² ³ Ž µ ¶ · ž ¹ º » Œ œ Ÿ ¿
À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï
Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß
à á â ã ä å æ ç è é ê ë ì í î ï
ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ
- Testing LC_MESSAGES with perror(), but it's a libc message.
- Implicitly setting LC_CTYPE by LANG succeeded.
- Implicitly setting LC_NUMERIC by LANG succeeded.
- Implicitly setting LC_TIME by LANG succeeded.
- Implicitly setting LC_COLLATE by LANG succeeded.
- Implicitly setting LC_MONETARY by LANG succeeded.
- Implicitly setting LC_MESSAGES by LANG succeeded.
Mind you, what you will actually see might depend eventual broken
mailer settings, missing characters in fonts etc.
But I can write cedille, ae, oe, a-ring, several vowels with
trema and even € EURO.
c
--
_B A U S T E L L E N_ lesen! --- http://www.blacktrash.org/baustellen.html
Re: Other European languages on a US keyboard
My text was I think misleading. I meant to say that accents were neither here nor there in the arrangement of the keys. The French didn't choose the AZERTY arrangement of the keyboard on the basis of using or not using accents, but only because, presumably, it was the best solution to the stuck hammer problem. At least, that is what I surmised. And, unacquainted with day-to-day English life as most Americans, I don't always know what was decided there and what here (in the US), though I'm never arrogant enough to think that it's all been decided here. (Actually, and despite living in Paris for 6 years, I'm something of an Anglophile, but that's another story--check out my Inspector Morse site at http://www.windofkeltia.com/morse and my Allo, Allo page at http://www.windofkeltia.com/allo .) Russ A.J.Mechelynck wrote: Russell Bateman wrote: Of course, we all realize that the original difference between AZERTY and QWERTY was the analyzed solutions to the problem of the likelihood of two typewriter hammers striking the platen in close enough succession that they would jam together and get stuck. Accents arose as a distinction only because the French decided, based presumably on a letter frequency analysis that AZERTY was the optimal key arrangement based on letter frequency in French words while Americans (I've never noticed what they type on in England) chose QWERTY. It was always a puzzle to me in my childhood as to why the keys weren't arranged in a more obvious fashion. It wasn't answered until, as I was acquainted with the Dvorak key layout, it was explained to me why typewriter keys had been arranged like that in the first place. Of course, now, it's all just tradition--strong enough that the Dvorak guys haven't carried the day and the chording guys are just a lone voice in the wilderness. I don't follow what you're saying about accents (typo?). The French have used accented letters since (IIUC) before Gutenberg invented printing. Yes, the various typewriter keyboards are supposed to be the result of some ergology research, but I don't know the details. IIRC the QWERTY keyboard was invented in England at a time when that was the leading industrial country in the world. W is quite rare in French while -ez is part of the universal second-person-plural ending of verbs; but wouldn't the latter make one think that placing z next to e (well, next on the keyboard, and separated by only S 3 X in the machinery) would cause _more_ jamming in mechanical typewriters? The q is safely away from the u... Best regards, Tony.
Re: Problem starting up vim: No mapping found
Charles E Campbell Jr wrote: Tobias Herp wrote: My vim version (SuSE Linux 9.1): VIM - Vi IMproved 6.2 (2003 Jun 1, compiled Apr 6 2004 03:03:03) Included patches: 1-8, 10-12, 14-18, 20-21, 25-32, 34-35, 37, 40, 43-46, 48-55, 58-59, 61-65, 67-89, 91-98, 100-102, 104-106, 108-114, 117, 119-120, 122, 126, 129, 133, 135-137, 139, 143-155, 157-160, 162-172, 174-176, 178, 180-187, 189-193, 195-198, 200-204, 206-209, 213, 216-224, 228-229, 231-232, 234, 237-242, 244-251, 253-263 Compiled by [EMAIL PROTECTED] Yakov gave you good advice; here's some more: build vim 7.0 . ... and Dr. Chip gave good advice too: since the 6.2 you're using, versions 6.3 and 6.4 have already come and gone, 7.0 has gone from alpha to release status, and it is currently at its 42nd bugfix. After trying and junking what had come with my SuSE 9.3, I'm currently using: VIM - Vi IMproved 7.0 (2006 May 7, compiled Jul 23 2006 22:50:51) Included patches: 1-42 Compiled by [EMAIL PROTECTED] Huge version with GTK2-GNOME GUI. Features included (+) or not (-): etc. If you want step-by-step help about how to compile Vim on Unix-like systems, see my page http://users.skynet.be/antoine.mechelynck/vim/compunix.vim Also, since you'd indicated that you may have added something to your plugin/ftplugin directory, do a ls -tl in those two directories and find out what the most recent inclusions are. Temporarily remove it/them and see if your message disappears with them. Regards, Chip Campbell Best regards, Tony.
Re: Other European languages on a US keyboard
Christian Ebert wrote: * A.J.Mechelynck on Saturday, July 22, 2006 at 22:40:45 +0200: The French oe (o, e-dans-l'o) is not defined in the Latin1 encoding, neither in capitals (as for titles or if the word oeuf [egg] is the first of a sentence), nor in lowercase. You need UTF-8 for it, No. Just latin9 or ISO8859-15 (Look at the header of this mail). Mon cœur. This is on a Mac with a German keyboard, but using actually an American keyboard layout. I enter the œ with Alt-q (the Alt key on Mac keyboard corresponds to the Modifier key on other keyboards I believe). $ echo $LANG en_US.ISO8859-15 [...] Good to know that the Euro sign wasn't the only missing glyph added in ISO 8859-15. There is an Alt key left of the spacebar on i86 machine's keyboards, but I guess you mean the Alt-Gr which is right of the spacebar. (Alt-something is used for menu shortcuts here.) AltGr-q gives me æ (aelig;), with shift Æ (AElig;). I think I'm going to experiment with this AltGr key, apparently it gives a lot of new characters not always mentioned on the keys; and different ones depending on whether it is used alone or with Shift. [after trying] I can't find oelig;, I will have to continue pasting it from Vim when I want it in an email. Best regards, Tony.
RE: Other European languages on a US keyboard
I haven't been following this thread in its entirety, but there are the Windows Alt Keycodes that can solve your entry of the œ symbol, and many others. To enter œ all you need to do is HOLD Alt, and then enter 0156 on the keypad, and then release Alt. Hardly a stylish solution, but easier than copy/pasting from Vim, I'm sure. Max -Original Message- From: A.J.Mechelynck [mailto:[EMAIL PROTECTED] Sent: Monday, July 24, 2006 3:58 PM To: vim@vim.org Subject: Re: Other European languages on a US keyboard Christian Ebert wrote: * A.J.Mechelynck on Saturday, July 22, 2006 at 22:40:45 +0200: The French oe (o, e-dans-l'o) is not defined in the Latin1 encoding, neither in capitals (as for titles or if the word oeuf [egg] is the first of a sentence), nor in lowercase. You need UTF-8 for it, No. Just latin9 or ISO8859-15 (Look at the header of this mail). Mon cœur. This is on a Mac with a German keyboard, but using actually an American keyboard layout. I enter the œ with Alt-q (the Alt key on Mac keyboard corresponds to the Modifier key on other keyboards I believe). $ echo $LANG en_US.ISO8859-15 [...] Good to know that the Euro sign wasn't the only missing glyph added in ISO 8859-15. There is an Alt key left of the spacebar on i86 machine's keyboards, but I guess you mean the Alt-Gr which is right of the spacebar. (Alt-something is used for menu shortcuts here.) AltGr-q gives me æ (aelig;), with shift Æ (AElig;). I think I'm going to experiment with this AltGr key, apparently it gives a lot of new characters not always mentioned on the keys; and different ones depending on whether it is used alone or with Shift. [after trying] I can't find oelig;, I will have to continue pasting it from Vim when I want it in an email. Best regards, Tony.
Re: edit-with-vim context menu item disappeared with vim7 upgrade
Michael Sorens wrote:
Did not see gvimext.reg in the binary, so I experimented some more.
After staring at install.exe some more, I realized I had not told it to make
any changes. But doing it correctly, it *still* did not update my registry!
So I then tried uninstalling and re-installing the entire vim 7.0. But again,
no luck.
Finally, I manually added the registry entries, as detailed in :help
install-registry and that fixed the problem. (Note that the last step in the
help text is out of date--it refers to vim 5.6, so I just skipped that one!)
You may want to add it mutatis mutandis, s/5.6/7.0/g ; the {path} in the
value will also end up in vim70 rather than vim56 of course. (There is
an uninstal program in 7.0 too.)
Best regards,
Tony.
Re: using syntax match two time in one line? fst blocks snd?
Hi Marc, I am assuming that you have output like this: --- | Field1 | Field2 | Field3 | Field4 | ... | --- | Value1 | Value2 | Value3 | Value4 | ... | --- In which case you might want to try something like this: syntax match Border '^-\+$' syntax match Border '^|' nextgroup=Col1 syntax match Col1 '[^|]\+|' contained nextgroup=Col2 syntax match Col2 '[^|]\+|' contained nextgroup=Col3 syntax match Col3 '[^|]\+|' contained nextgroup=Col4 syntax match Col4 '[^|]\+|' contained [ ... etc ... ] syntax match Border | contained containedin=Col1,Col2,Col3,Col4 hi link Border Error hi link Col1 Macro hi link Col2 Type hi link Col3 Statement hi link Col4 String [ ... etc ... ] This should highlight each column in a different color for you. In case this doesn't help you, the following might help you: - using '^' in your pattern means it can *only* match at the beginning of the line - you don't need to use \ze at the end of your pattern. Typically \ze is used when you want the match to end there, but you want to make sure some other things following \ze also match. 'foo\zebar' matches and 'foo', but only if it is followed by 'bar'. - rather than adding the whole 'skip over first col' pattern stuff to the Color2 match, why not add 'nextgroup=Color2' to the end of the Color1 match? HTH, regards, Peter --- Marc Weber [EMAIL PROTECTED] wrote: background: I want to highlight columns in a table differently (database output) So 1 and 2 will be substituted by either \t or |. = syntax file == hi def link Color1 Macro hi def link Color2 Error Show colors of Color1, Color2 syn keyword Color1 A syn keyword Color2 B syn match Color1 '^1\zs[^1]*\ze' syn match Color2 '^1[^1]*1\zs[^1]*\ze' syn match Color2 '^2[^2]*2\zs[^2]*\ze' = testfile = A B 1aa1bb 2cc2dd explanation lines testfile: Line 1 testline to show Color1 Line 2 testfile to show Color2 Line 3 Here aa and bb should be highlighted with Color1, Color2 ( bb isn't) Line 4 only dd should be highlighted to show that the match pattern works (only difference is 2 instead of 1) Marc Send instant messages to your online friends http://au.messenger.yahoo.com
Re: I lost gvim on a Debian/testing
ahmet nurlu wrote: Hi, I am an user of gvim on a Debian/testing. I mistakenly deleted some vim, gvim related directories like /etc/vim, /etc/gvim. After that, I was unable to run gvim. Whenever I run it , I always get the vim without gui. I tried reinstall vim-gnome by giving a command apt-get install --reinstall vim-gnome on a console. But no success. It still runs the vim without gui. [...] Try which -a vim which -a gvim in the shell, to see all programs of those names in the $PATH. The first one listed for each name will get invoked when you don't mention a path on the shell command line. Then, ls -l `which -a vim` `which -a gvim` will tell you (but not necessarily in the same order as before) when each of the above was compiled, its size, and, if it's a link, what it points to. You might try to compile Vim for yourself. It's not difficult, see http://users.skynet.be/antoine.mechelynck/vim/compunix.vim , and it will allow you to always have the latest version, tailored to your needs and wants, and with your name on it. Unless you specify another installdir, it will install the Vim runtime files in /usr/local/share/vim/vim70 and the binary in /usr/local/bin -- but don't take my word for it, check it as above. To use a single GUI-enabled executable as both gvim and console Vim, install it as vim (like above) and add a link to it. Similarly for other Vim executable names: for instance: pushd /usr/local/bin # does it exist here ? ls -l vim # is it GUI-enabled ? ./vim --version |more # check near the beginning of the output # if it tells you with or without GUI. # if it says without GUI you cannot use it for gvim # if OK: ln -s vim gvim ln -s vim vi ln -s vim ex ln -s vim view ln -s vim gview ln -s vim vimdiff ln -s vim gvimdiff # etc. (see the list starting at :help ex). ls -l popd Best regards, Tony.
Re: Other European languages on a US keyboard
Max Dyckhoff wrote: I haven't been following this thread in its entirety, but there are the Windows Alt Keycodes that can solve your entry of the œ symbol, and many others. To enter œ all you need to do is HOLD Alt, and then enter 0156 on the keypad, and then release Alt. Hardly a stylish solution, but easier than copy/pasting from Vim, I'm sure. Max Except that I never remember those numbers. -Vim is intuitive: To enter œ in Vim, I hit ^Koe (where ^K is Ctrl-K). No weird numbers to remember, just one ctrl-key for all digraphs. And is it possible even on Windows to use codes above 255 (in this case, Alt-0339 I suppose)? -Vim is customizable: When I want to type Russian, I use gvim with my own russian-phonetic_utf-8.vim keymap, where a maps to ah, b to beh, v to veh, g to gheh, etc. No weird keystrokes to remember. -Vim is cross-platform: On this SuSE Linux system, Alt-keypad codes just don't work. Vim, OTOH, works the same on both Windows and Linux. Morality: Don't underrate Vim, especially not on its own mailing list. :-) Best regards, Tony.
Re: edit-with-vim context menu item disappeared with vim7 upgrade
OK; wasn't sure if that was just obsolete or not... Thanks for your guidance!
Re: Other European languages on a US keyboard
cga2000 wrote: On Mon, Jul 24, 2006 at 05:59:42PM EDT, Christian Ebert wrote: * A.J.Mechelynck on Saturday, July 22, 2006 at 22:40:45 +0200: The French oe (o, e-dans-l'o) is not defined in the Latin1 encoding, neither in capitals (as for titles or if the word oeuf [egg] is the first of a sentence), nor in lowercase. You need UTF-8 for it, No. Just latin9 or ISO8859-15 (Look at the header of this mail). Mon coeur. This is on a Mac with a German keyboard, but using actually an American keyboard layout. I enter the oe with Alt-q (the Alt key on Mac keyboard corresponds to the Modifier key on other keyboards I believe). Could this be Mac-specific? I switched to encoding=latin9. When I do a Ctrl-K o e and a Ctrl-K O E this is what I get: ½ ¼ confirmed by the :dig command. I looked carefully at the output of :dig and I couldn't see our elusive e dans l'o either. So I switched to the French ISO-08859-15, then the US version of latin9.. still can't find that o dans l'e. Strange thing is that the font I use on terminals does have these two characters (upper/lower case E dans l'O..) in the exact same spot Vim displays the above fractions.. Try the following (in gvim): :echo has(multi_byte) the answer should be 1. If it is zero, your version of gvim cannot handle UTF-8. :if tenc== | let tenc = enc | endif | set enc=utf-8 :new then i (set Insert mode) and ^Vu0153 (where ^V is Ctrl-V, unless you use Ctrl-V to paste, in which case it is Ctrl-Q). If you see anything other than the oe digraph, then your 'guifont' is plain wrong. See http://vim.sourceforge.net/tips/tip.php?tip_id=632 about how to choose a better one. Best regards, Tony.
Re: Other European languages on a US keyboard
On Mon, Jul 24, 2006 at 08:29:10PM EDT, A.J.Mechelynck wrote: cga2000 wrote: On Mon, Jul 24, 2006 at 05:59:42PM EDT, Christian Ebert wrote: * A.J.Mechelynck on Saturday, July 22, 2006 at 22:40:45 +0200: The French oe (o, e-dans-l'o) is not defined in the Latin1 encoding, neither in capitals (as for titles or if the word oeuf [egg] is the first of a sentence), nor in lowercase. You need UTF-8 for it, No. Just latin9 or ISO8859-15 (Look at the header of this mail). Mon coeur. This is on a Mac with a German keyboard, but using actually an American keyboard layout. I enter the oe with Alt-q (the Alt key on Mac keyboard corresponds to the Modifier key on other keyboards I believe). Could this be Mac-specific? I switched to encoding=latin9. When I do a Ctrl-K o e and a Ctrl-K O E this is what I get: ½ ¼ confirmed by the :dig command. I looked carefully at the output of :dig and I couldn't see our elusive e dans l'o either. So I switched to the French ISO-08859-15, then the US version of latin9.. still can't find that o dans l'e. Strange thing is that the font I use on terminals does have these two characters (upper/lower case E dans l'O..) in the exact same spot Vim displays the above fractions.. Try the following (in gvim): .. with all the goings-on in this thread I never had a chance to mention the fact that I do not use gvim. I try to do everything in a terminal (under gnu/screen) because text-mode apps were designed for the keyboard so they work a lot better than gui's for those of us who prefer not to use mice. :echo has(multi_byte) the answer should be 1. If it is zero, your version of gvim cannot handle UTF-8. Works fine if I switch my locale to UTF-8. Vim automatically figures what I want and :dig displays the o dans l'e (both the lower and upper case versions) among a gazillon other digraphs. Then I can use the ususal Ctrl-K oe .. save the file.. pass this on to LaTeX and provided I have the correct LaTeX statements to activate UTF-8 (that's what took forever to figure out the other day..) I get my coeurs, voeux and boeufs rendered correctly in xdvi/gv .. *and* the the ensuing printout looks great too. The problem with this is that I haven't found a comfortable way to run Vim in UTF-8 mode and the rest of my stuff in 8-bit mode. Over the week-end I found that I can run Vim in a separate unicode xterm but that's not what I want because I lose screen's copy/paste and more importantly it destroys my attempt at running a fully integrated desktop. Other problems that I have run into is that text files created when in UTF-8 mode are a mess when browsed in latin1/9 mode. I also have problems when I print unicode files.. I once created a nice table with those box-drawing characters that were available in UTF-8 mode and it was really nice on-screen.. but when I tried to print it, all I got was rows and columns of questiion marks. So I switched back to latin1 pending better internationalization support in some applications (slrn, ELinks.. mutt should workd but it's tricky) and maybe more importantly until I acquire a better understanding of running a unicode locale in X/linux and the implications thereof.. :if tenc== | let tenc = enc | endif | set enc=utf-8 :new then i (set Insert mode) and ^Vu0153 (where ^V is Ctrl-V, unless you use Ctrl-V to paste, in which case it is Ctrl-Q). If you see anything other than the oe digraph, then your 'guifont' is plain wrong. See http://vim.sourceforge.net/tips/tip.php?tip_id=632 about how to choose a better one. Well.. actually.. I ran some tests in latin-9 earlier.. trying to figure out this o dans l'e business.. that was on a linux console.. and that's where I realized that I was still running a unicode font.. both on the linux console and in 'X'.. :-) .. It seems I never switched back after my brief incursion into unicode territory.. and since I haven't had any problems displaying and printing text since I switched back.. I would say that the font is ok.. And that UTF-8 stuff is indeed backward-compatible? The font is called terminus and I like it a lot because it looks like a fixed-width version of MS's Verdana, which is my favorite screen font. see http://.geocities.com/cga/wee.png for an excellent screenshot. Thanks cga
Re: Other European languages on a US keyboard
cga2000 wrote: On Mon, Jul 24, 2006 at 08:29:10PM EDT, A.J.Mechelynck wrote: cga2000 wrote: On Mon, Jul 24, 2006 at 05:59:42PM EDT, Christian Ebert wrote: * A.J.Mechelynck on Saturday, July 22, 2006 at 22:40:45 +0200: The French oe (o, e-dans-l'o) is not defined in the Latin1 encoding, neither in capitals (as for titles or if the word oeuf [egg] is the first of a sentence), nor in lowercase. You need UTF-8 for it, No. Just latin9 or ISO8859-15 (Look at the header of this mail). Mon coeur. This is on a Mac with a German keyboard, but using actually an American keyboard layout. I enter the oe with Alt-q (the Alt key on Mac keyboard corresponds to the Modifier key on other keyboards I believe). Could this be Mac-specific? I switched to encoding=latin9. When I do a Ctrl-K o e and a Ctrl-K O E this is what I get: ½ ¼ confirmed by the :dig command. I looked carefully at the output of :dig and I couldn't see our elusive e dans l'o either. So I switched to the French ISO-08859-15, then the US version of latin9.. still can't find that o dans l'e. Strange thing is that the font I use on terminals does have these two characters (upper/lower case E dans l'O..) in the exact same spot Vim displays the above fractions.. Try the following (in gvim): .. with all the goings-on in this thread I never had a chance to mention the fact that I do not use gvim. I try to do everything in a terminal (under gnu/screen) because text-mode apps were designed for the keyboard so they work a lot better than gui's for those of us who prefer not to use mice. Gvim can use keyboard commands just like console Vim, or mice-addicted people can use that too. It has a lot more different coulours (typically 16 million rather than 16) and it can change fonts on-the-fly (change the font from Courier to Lucida to whatever, only through Vim keyboard commands). It can do real boldface and italics, as well as straight or curly underlining. And it can use Unicode: see further down. :echo has(multi_byte) the answer should be 1. If it is zero, your version of gvim cannot handle UTF-8. Works fine if I switch my locale to UTF-8. Vim automatically figures what I want and :dig displays the o dans l'e (both the lower and upper case versions) among a gazillon other digraphs. Then I can use the ususal Ctrl-K oe .. save the file.. pass this on to LaTeX and provided I have the correct LaTeX statements to activate UTF-8 (that's what took forever to figure out the other day..) I get my coeurs, voeux and boeufs rendered correctly in xdvi/gv .. *and* the the ensuing printout looks great too. The problem with this is that I haven't found a comfortable way to run Vim in UTF-8 mode and the rest of my stuff in 8-bit mode. Well, in an xterm (or konsole, or Windows Dos Box), console Vim is dependent on xhatever charset the console is using. If you xterm (or whatever) is in Latin1, you cannot use French oe anymore than you can use Cyrillic or Greek. Gvim, on the other hand, can display anything for which you have a glyph in a font. Over the week-end I found that I can run Vim in a separate unicode xterm but that's not what I want because I lose screen's copy/paste and more importantly it destroys my attempt at running a fully integrated desktop. Other problems that I have run into is that text files created when in UTF-8 mode are a mess when browsed in latin1/9 mode. I also have problems when I print unicode files.. I once created a nice table with those box-drawing characters that were available in UTF-8 mode and it was really nice on-screen.. but when I tried to print it, all I got was rows and columns of questiion marks. So I switched back to latin1 pending better internationalization support in some applications (slrn, ELinks.. mutt should workd but it's tricky) and maybe more importantly until I acquire a better understanding of running a unicode locale in X/linux and the implications thereof.. :if tenc== | let tenc = enc | endif | set enc=utf-8 :new then i (set Insert mode) and ^Vu0153 (where ^V is Ctrl-V, unless you use Ctrl-V to paste, in which case it is Ctrl-Q). If you see anything other than the oe digraph, then your 'guifont' is plain wrong. See http://vim.sourceforge.net/tips/tip.php?tip_id=632 about how to choose a better one. Well.. actually.. I ran some tests in latin-9 earlier.. trying to figure out this o dans l'e business.. that was on a linux console.. and that's where I realized that I was still running a unicode font.. both on the linux console and in 'X'.. :-) .. It seems I never switched back after my brief incursion into unicode territory.. and since I haven't had any problems displaying and printing text since I switched back.. I would say that the font is ok.. And that UTF-8 stuff is indeed backward-compatible? The font is called terminus and I like it a lot because it looks like a fixed-width version of MS's Verdana, which is my favorite screen font. see
Re: Problem starting up vim: No mapping found
A.J.Mechelynck [EMAIL PROTECTED] said: Charles E Campbell Jr wrote: Tobias Herp wrote: [...] If you want step-by-step help about how to compile Vim on Unix-like systems, see my page http://users.skynet.be/antoine.mechelynck/vim/compunix.vim I found it at this address: http://users.skynet.be/antoine.mechelynck/vim/compunix.htm Also, since you'd indicated that you may have added something to your plugin/ftplugin directory, do a ls -tl in those two directories and find out what the most recent inclusions are. Temporarily remove it/them and see if your message disappears with them. Regards, Chip Campbell Best regards, Tony.
tabpages and bufdelete
Hi , I am using tabpages. In a given tabpage, I have open lots of buffers. I want to quit only one buffer in a tabpage. If I type : :q Then the whol, tabpage is quit. Even if I type bdel , then also the complete tabpage is deleted. How do I quit only a single buffer. Regards, Shankar
Re: Problem starting up vim: No mapping found
DogWalker wrote: A.J.Mechelynck [EMAIL PROTECTED] said: Charles E Campbell Jr wrote: Tobias Herp wrote: [...] If you want step-by-step help about how to compile Vim on Unix-like systems, see my page http://users.skynet.be/antoine.mechelynck/vim/compunix.vim I found it at this address: http://users.skynet.be/antoine.mechelynck/vim/compunix.htm Oops, yes. Typing faster than I was thinking. Of course it's .htm not .vim Best regards, Tony.
Re: tabpages and bufdelete
SHANKAR R-R66203 wrote: Hi , I am using tabpages. In a given tabpage, I have open lots of buffers. I want to quit only one buffer in a tabpage. If I type : :q Then the whol, tabpage is quit. Even if I type bdel , then also the complete tabpage is deleted. How do I quit only a single buffer. Regards, Shankar To replace the current window by an empty window :enew To delete a buffer, but avoid quitting the tabpage if it has only 1 window let cur_buf = bufname(%) if tabpagewinnr(tabpagenr(), $) == 1 enew endif exe bdel cur_buf Note that :bdel does not really delete a buffer, it just makes it invisible (hides it from :ls unless you use a bang, etc.). Only :bw[ipeout] truly deletes all traces of a buffer. Or, depending on what you want to do, you could do: if tabpagewinnr(tabpagenr(), $) == 1 enew else quit endif see :help enew :help tabpagenr() :help tabpagewinnr() Best regards, Tony.
