Re: Why bottom-posting is prefered on Vim Mainling List?
Hi [EMAIL PROTECTED], *, You got many answers concerning the technical aspects of top-bottom-inline answers. Apart of that, there ist another one.. A mailinglist is kept alive from two parts: people having questions _and_ people having answers. The latter ones often are lurking on several mailinglist reading hundreds of mails a day.. [EMAIL PROTECTED] schrieb: >Hi vimmers: > >Slightly Off-topic, but I'm still wondering why bottom-posting is > prefered on Vim Mainling List. [..] >and I personally > feel top-posting much much easier to read than bottom-posting. ..if You are one _having_ questions that doesn't matter very much, as long as You are interested in getting good answers. ;o)) Aparently a wide range of those more experienced people get their work done more rapidly an efficiently if they are fed with well trimmed and structured inline answered mails. So your chance for getting a valid and useful answer is growing with the number of readers, which can get the point of Your question and the following discussion with a short view. If You _have_ good answers it's up to You, how to spit them out - they will be read however ;o)) >Is there any point (or historic reason) choosing bottom-post ? It seems to be some general experience for Mailinglist/Newsgroup traffic that things work better choosing inline answers. As far as I literally understand "bottom post" I am with You: I can't see any advantage putting the whole answer at the bottom of the mail. But perhaps as non native speaker I don't understand "bottom" well. btw. I join the voices that price the nice way people are discussing even that (off-)topic on this list. Vimmers seem to be a special kind of civilized people. :o)) -- Friedrich Schöne Grüße / best regards from south part of Germany
Re: Identify this Vim font for me, please
Hi madiyaan, *, madiyaan schrieb: >Hello, > >This isn't very related to Vim, but I found this font on Vim's > wikipedia webpage: > >http://upload.wikimedia.org/wikipedia/commons/8/8c/Vim-%28logiciel%29console.png >Can anyone identify this font for me? It's called "console" and I'm using it every day. >It looks very good for programming. Oh, it *is*! :o)) But as you read: tastes are different ;o)) It works fine here in my linux environment. regards -- Friedrich Schöne Grüße von der Schwäbischen Alb
Re: syntax for vcard/vcf files
Hi Andy, *, Andy Wokula schrieb am Mittwoch, 10. Januar 2007 13:11: >Friedrich Strohmaier schrieb: >> Hello everybody, >> A happy new year to all vimmers. :o) >> >> I am looking for a syntax highlighting file for vcard/vcf files. >> Nor $searchengine nor vim.org could give me advice. >> >> Does somebody know about syntax highlighting for vcard/vcf files? >> >> Friedrich > >But there is a syntax file ... I never had doubts for that ;o)) > >Google Search on Vim pages > >|vcard_| [Google Search] > >(*) Search www.vim.org ah! > >http://www.vim.org/scripts/script.php?script_id=1455 that's I was looking for.. > >Die Bewertung ist allerdings nicht besonders gut. macht nix - für mich reicht's / doesn't matter! Gruß & thx Friedrich
syntax for vcard/vcf files
Hello everybody, A happy new year to all vimmers. :o) I am looking for a syntax highlighting file for vcard/vcf files. Nor $searchengine nor vim.org could give me advice. Does somebody know about syntax highlighting for vcard/vcf files? Friedrich
Re: What might cause .vimrc not to be read
Hallo [EMAIL PROTECTED], *, [EMAIL PROTECTED] schrieb am Freitag, 23. Juni 2006 21:43: [..] >Is there something in vim similar to emacs where you can just say >`dark background' or `light bg' and get a default setup that is not >bad? Well, up to now I was quite happy doing vim :set bg=light/dark depending on a light/dark background. Probably this is, what you are looking for.. > >I'm not all that picky about the syntax hilight colors only that I >really don't like dark blue on a black xterm. It seems to disappear >to me. There are a few other colors that don't work well on a black >xterm too but mostly some sensible dark background default would >probably be fine. for me exactly that works. Hope I got your problem. Friedrich
Re: marked text in visual mode is loaded to xclipboard
Hi Tony, *, A.J.Mechelynck schrieb am Mittwoch, 17. Mai 2006 00:51: >Friedrich Strohmaier wrote: >[...] > >> So simple and so far away! I was searching, but had no luck to hit. > >[...] > >You might have tried ":helpgrep clipboard" after all else had failed. another one new for me and much closer than $search_engine Think I'll stay subscribed ;o)) Regards Friedrich
Re: marked text in visual mode is loaded to xclipboard
Hello Yegappan, *, Yegappan Lakshmanan schrieb am Dienstag, 16. Mai 2006 20:56: >Hello, > >On 5/16/06, Friedrich Strohmaier <[EMAIL PROTECTED]> wrote: [..] >> Try the following (in normal mode): >> 1. Take text from anywhere with the mouse >> 2. clear the target area and enter insert mode typing "v", "l", >> "s" 3. paste with middle mouse button >> >> result: You get the text vom cleared area -- anoying!! >> expected result: the anywhere fetched text should be pasted. >> >> I noticed that behavior since vim 6.x Well then, I was wrong: aparently it wasn't a change of vim, it seems to be a unknown "benefit" from my new distributor's package maintainer. >> >> This apears in console-vim (xterm) an gvim. >> using a virtual tty with gpm works as expected. >> >> Can anyone help me to find the right option to be set, or to file a >> bugreport. I subscribed here to get feedback/confirmation before >> bothering the developers. >> >> Any hints? > >When you make a visual selection, Vim will copy the selected text to >the clipboard. This is controlled by the 'clipboard' option in > terminal Vim and by the 'guioptions' option in GUI Vim. To disable > Vim from copying the visually selected text to clipboard, use the > following commands: > >set clipboard= >set guioptions-=a So simple and so far away! I was searching, but had no luck to hit. > >You can place the first command in the .vimrc file and the second one >in the .gvimrc file. > >For more information about this, read > > :help 'clipboard' > :help guioptions_a that's it - you make me happy ;o)) Regards from Germany Friedrich
marked text in visual mode is loaded to xclipboard
Hi alltogether, I'm new to this list, but not new to vim, so let me say "hello" to everybody. I'm not that poweruser, but I hate unnecesary repeating things and vim allways gave me, what I needed :o)) Im working on ubuntu-linux 5.10 with the boxed vim Version 6.3.78 I subscribed this list to get ahead with a problem, which drives me crasy nearly everytime I work with vim: If I mark some text in visual mode that text is put in the x-clipboard and therefore pasted with the mouse on the action following. Try the following (in normal mode): 1. Take text from anywhere with the mouse 2. clear the target area and enter insert mode typing "v", "l", "s" 3. paste with middle mouse button result: You get the text vom cleared area -- anoying!! expected result: the anywhere fetched text should be pasted. I noticed that behavior since vim 6.x This apears in console-vim (xterm) an gvim. using a virtual tty with gpm works as expected. Can anyone help me to find the right option to be set, or to file a bugreport. I subscribed here to get feedback/confirmation before bothering the developers. Any hints? Friedrich more info about my vim: $ vim --version VIM - Vi IMproved 6.3 (2004 June 7, compiled Aug 22 2005 17:27:07) Included patches: 1-78 Compiled by [EMAIL PROTECTED] Big version with GTK2 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_gui +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_interact +xterm_clipboard -xterm_save system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" user exrc file: "$HOME/.exrc" system gvimrc file: "$VIM/gvimrc" user gvimrc file: "$HOME/.gvimrc" system menu file: "$VIMRUNTIME/menu.vim" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/freetype2 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -O2 -g -Wall -I/usr/include/python2.4 -pthread Linking: gcc -L/usr/local/lib -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lXinerama -lXi -lXrandr -lXext -lXcursor -lXfixes -lpango-1.0 -lfreetype -lz -lcairo -lXrender -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lXt -lncurses -lgpm -L/usr/lib/python2.4/config -lpython2.4 -lutil -lm -Xlinker -export-dynamic
