Re: scrolloff enhancement wish
Yakov Lerner wrote: Would you include into todo.txt the thing that I used in one very ancient but exceptionally smooth editor called K52 (it worked on pdp11, vt52 terminals). This editor always positioned cursor at 2/3 height from top of screen. This worked surprisingly well, even if it sounds strange. I worked couple of years with this editor and this felt very comfortable. How about adding the option 'scrollfix' [to the todo.txt], which would fix the cursor on fixed line, in percantage 0-100. Value ':set scrollfix=50' would work like ':set scrolloff=999'. Value ':set scrollfix=67' would fix cursor 2/3 from top of screen. Value ':set scrolloff=0' would keep cursor at top line of screen. Value ':set scrolloff=100' would keep cursor at bottom line of screen. Would you put this into todo.txt ? As you say, you can already do most of this by setting 'scrolloff' to a large number. If the cursor is really fixed at one position then using j would mean that the cursor remains in the same position and the text scrolls. That goes against what most people expect. I think it's not all that useful. And we have too many options already... -- hundred-and-one symptoms of being an internet addict: 33. You name your children Eudora, Mozilla and Dotcom. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: scrolloff enhancement wish
On Fri, Jul 21, 2006 at 10:02:10AM +0200, Bram Moolenaar wrote: Yakov Lerner wrote: How about adding the option 'scrollfix' [to the todo.txt], which would fix the cursor on fixed line, in percantage 0-100. Value ':set scrollfix=50' would work like ':set scrolloff=999'. Value ':set scrollfix=67' would fix cursor 2/3 from top of screen. Value ':set scrolloff=0' would keep cursor at top line of screen. Value ':set scrolloff=100' would keep cursor at bottom line of screen. As you say, you can already do most of this by setting 'scrolloff' to a large number. If the cursor is really fixed at one position then using j would mean that the cursor remains in the same position and the text scrolls. That goes against what most people expect. I think it's not all that useful. I've had some situations where such a feature would be useful. A few weeks ago I was working with a large file containing many long SQL statements mixed in amongst other stuff. I was searching for the start of each statement, and it would have been very useful if I could have arranged it so that each search resulted in the cursor appearing a couple of lines from the the top of the screen with the SQL statement filling the space below it. In this case I set scrolloff to 100 so the start of each SQL statement was centred, but that gave me half a screen of context above the cursor when only two or three lines would have done, and caused the ends of the longest SQL statements to disappear below the bottom of the screen. I suppose there might be some way to map all the movement commands to reposition the current line to a certain place on the screen, but at the time I was doing all this it was quicker to scroll the text each time than it would have been to write all the necessary mappings. And we have too many options already... Too many options? Is that possible? -- Matthew Winn ([EMAIL PROTECTED])
Re: poll?
Dnia czwartek, 20 lipca 2006 23:55, Bram Moolenaar napisał: Yakov Lerner wrote: Bram, How about posting a poll on www.vim.org site ? Two polls ! (1) Do you you vim6 or vim 7 ? (2) Do you use console-mode-vim or gvim ? What would we do with the outcome? While I don't understood reason for first poll second should give insight what todo items should get bigger priority. Although console/gvim choice mostly depends on system. To get more significant results it should be more like: - console version on MS-Windows - GUI version on MS-Windows - console version on all other systems - GUI version on all other systems m.
Crazy wish: vimcat
Is this possible? It just occurred to me that it would be great if there was a VIM-related program that would 'cat' in color using VIM's highlighting rules. Is this something that VIM could be made to do via scripting, or would it need to be a totally new program? If the latter, any guesses how hard it would be to make such a critter? I notice that echo ':q' | vim file sort-of works... it gives the first page, plus trailing '~'s (if less then a page), although this wouldn't work with TERM's where curses displays are a separate buffer (like 'xterm', but not 'linux'). -- Matthew Doom doom dooM doo-DooM dOOm DOom doOM... DOOM! -- Gir
Re: poll?
On Friday, July 21 at 07:11 PM, quoth A.J.Mechelynck: Mikolaj Machowski wrote: Dnia czwartek, 20 lipca 2006 23:55, Bram Moolenaar napisał: Yakov Lerner wrote: Bram, How about posting a poll on www.vim.org site ? Two polls ! (1) Do you you vim6 or vim 7 ? (2) Do you use console-mode-vim or gvim ? What would we do with the outcome? While I don't understood reason for first poll second should give insight what todo items should get bigger priority. Isn’t that the entire purpose of http://www.vim.org/sponsor/vote_results.php ? ~Kyle -- There in America we are descended in blood and in spirit from revolutionist and rebel men and women who dare to dissent from accepted doctrine. As their heirs, may we never confuse honest dissent with disloyal subversion. -- Dwight D. Eisenhower pgpGmX9I8CePw.pgp Description: PGP signature
Re: Visible Spaces
This is what I'd thinked about. IMO, Consider use the Underlined group, The underlined is not a character, but it looks like a character. I guess this suit Johnson's need better. HTH -- Sincerely, Pan, Shi Zhu. ext: 2606 Benji Fisher [EMAIL PROTECTED] wrote on 2006.07.21 13:56:55: Would you be satisfied with changing the background color for spaces? Step 1: :hi and look for a pleasing color. I am not using the GUI right now, and it looks as though my choices are limited. (Many groups change the foreground color but not the background, at least in the default color scheme with my terminal.) I will choose DiffChange . Second step: :match DiffChange / / Ahh! That looks awful, so :match NONE will get me back to normal. HTH --Benji Fisher P.S. I think that :match NONE only works with vim 7.0, but I think the rest works with vim 6.x. On Fri, Jul 21, 2006 at 11:48:45AM +0800, Stewart Johnson wrote: Thanks guys! Intermediate spaces were what I was looking for, oh well. :-/ On 7/21/06, Steve Hall [EMAIL PROTECTED] wrote: On Fri, 2006-07-21 at 11:19 +0800, Stewart Johnson wrote: Is there a vim option to represent space characters in a file as a dot or something else not blank? Vim can only represent trailing spaces, not any intermediate ones. (Per the previously mentioned listchars option.) -- Steve Hall [ digitect dancingpaper com ]
Re: Awareness of python import semantics for [i, etc.?
On Thu, Jul 20, 2006 at 11:07:48AM -0700, John Reese wrote: Actually, you can't actually tell that from the import line. blag could also be a package (i.e. directory) containing a module Bok, defined in a file called Bok.py. That's what I had in mind. The following is an example of the kind of import line I'm talking about, which imports a module from a package: from xml.dom import domreg # effectively the same as 'import xml.dom.domreg as domreg' # but the from ... import ... form is much more common domreg module 'xml.dom.domreg' from '/...' The clause after from is the directory (after includeexpr turns the dots into slashes), and the clause after import is the filename (after .py from suffixesadd is added), and I guess all I'm saying is I think having directory name and filename be in separate words might break assumptions in the *include-search* mechanism. I can add the base directory plus **/ to 'path', but that's a lot slower than just adding the base directory and configuring the include-search mechanism to know how to join up the whole import line to get the relative path. Anyway, at this point I feel like I should just go off and dink around for a while and see if I can get something to work. Thanks for your help. Have you read :help 'include' carefully? I think that what you want is something along the lines of :let l:include = '^\s*from\s\+\zs' (untested). Then, if I read the docs correctly, you should be able to pass xml.dom import domreg to 'includeexpr'. I suggest using 'includeexpr' to call a function, and putting all the conditionals and substitute()'s in the function. Note that I use :let to avoid the problem of escaping back-slashes in a :set command. Then l: has the same effect as :setlocal . If you get this to work, please send it to the maintainer of ftplugin/python.vim . I think others would like to use it, too. HTH --Benji Fisher
Re: edit-with-vim context menu item disappeared with vim7 upgrade
My next step, I suppose is to review all the relevant registry keys, but I wanted to see if there were other thoughts on this...? At least in the source, there is a GvimExt.reg file. You can edit this file (add absolute paths) and add it to the registry (double-clicking on it should do that). install.exe appears to be kind of non-working here. Thomas.
How can I know difference between Vim6.3 and Vim 6.2?
Hi, This may be a silly question, but I had done a search and did not found the answer. The help version7 tells difference between version6 and version7 However, 6.1 and 6.2 has differences, 6.2 and 6.3 has differences, where is the document about differences between the minor versions? Thanks. -- Sincerely, Pan, Shi Zhu. ext: 2606
Perl::Tags (Was: perlcomplete.vim -- anyone working on this?
On Wed, 12 Jul 2006, Dr Bean wrote:
On Wed, 12 Jul 2006, Hakim Cassimally wrote:
Also... at the moment the script in the manpage doesn't have a mapping
to refresh the tags file. If you defined the sub after opening the
file, it won't be seen until you close and reopen. (I'll probably fix
this soon, but patches welcome :-)
Making s:do_tags a global function, Do_tags allows you to call it
yourself, call Do_tags(expand('%')).
I don't understand why this doesn't work when you source
perl.vim.
This autocommand refreshes the tags file when you write, but the
tags you have last written are the last ones you want to jump
to, so I don't think it is much use.
augroup perltags
au!
autocmd BufWritePost *.pm,*.pl call s:do_tags(expand('%'))
augroup END
I am more worried that Module::Locate doesn't find modules in lib/ and t/
--
Dr Bean You can lead a horse to water,
but you can't make it drink
unless you gallop it round first.
Re: How can I know difference between Vim6.3 and Vim 6.2?
Hi, [EMAIL PROTECTED] wrote: This may be a silly question, but I had done a search and did not found the answer. The help version7 tells difference between version6 and version7 However, 6.1 and 6.2 has differences, 6.2 and 6.3 has differences, where is the document about differences between the minor versions? :help version-6.3 Regards, Jürgen -- Jürgen Krämer Softwareentwicklung HABEL GmbH Co. KGmailto:[EMAIL PROTECTED] Hinteres Öschle 2 Tel: +49 / 74 61 / 93 53 - 15 78604 Rietheim-WeilheimFax: +49 / 74 61 / 93 53 - 99
Re: Visible Spaces
Steve Hall wrote: On Fri, 2006-07-21 at 11:19 +0800, Stewart Johnson wrote: Is there a vim option to represent space characters in a file as a dot or something else not blank? Vim can only represent trailing spaces, not any intermediate ones. (Per the previously mentioned listchars option.) Note I don't find this an issue as vim does highlight intermediate tabs, I use the following settings ~/.vimrc for visible whitespace: flag problematic whitespace (trailing and spaces before tabs) Note you get the same by doing let c_space_errors=1 but this rule really applys to everything. highlight RedundantSpaces term=standout ctermbg=red guibg=red match RedundantSpaces /\s\+$\| \+\ze\t/ use :set list! to toggle visible whitespace on/off set listchars=tab:-,trail:.,extends: Pádraig.
Re: gvimdiff and gvim 7 in windows
On Fri, Jul 21, 2006 at 01:19:56PM +0200, Robert Cussons wrote: gvimdiff part: In my .vimrc I have the line: set columns=88 lines=80 because this is the size I want my gvim window to be when it opens, however as gvimdiff opens at least two buffers I would like it to open full screen, is there a way of getting this to happen? I have this in my vimrc file: diff to open with horizontal splits. if diff au VimEnter * windo wincmd K if has(gui_running) let columns = columns + foldcolumn endif endif You could put whatever you want inside the test for diff mode. OTOH, I do not know how to maximize the window from a script, except when using W32. (Kluge: maximize, note the setting of 'lines' and 'columns', and then set to those values.) gvim 7 in windows part: [snip] Maybe someone else can answer this. HTH --Benji Fisher
RE: Visible Spaces
Would you be satisfied with changing the background color for spaces? Step 1: Ah, that's an idea. Just / to search for spaces (assumes highlighting's turned on), and they'll all be highlighted. He wants to turn off highlighting, just /qqq or something. Else maybe tweak the font to change space to middot; or something. Thing is, change the font to something else, and that goes away, and he'd have to tweak the font for that as well. Eg, if he's using Lucida console 10pt, make a copy of the font, rename to something else (Lucidaspace or whatever), edit the font to change the space char, then when you want visispaces, just font your way to that. Want invisispaces again, change back to the normal Lucida font.
Re: Visible Spaces
On 21 Jul 2006, at 05:19, Stewart Johnson wrote: Hi All - Sorry if this obvious but I couldn't find anything in :help or google. Is there a vim option to represent space characters in a file as a dot or something else not blank? Thanks, Stewart :set hls / That is slash then a space ;-) Jerry
Re: gvimdiff and gvim 7 in windows
Robert Cussons wrote:
gvimdiff part:
In my .vimrc I have the line:
set columns=88 lines=80
because this is the size I want my gvim window to be when it opens,
however as gvimdiff opens at least two buffers I would like it to open
full screen, is there a way of getting this to happen?
gvim 7 in windows part:
I also use gvim at home, but there I use gvim 7 on windows instead of
gvim 6.3 on debian. So I have a few questions:
How do I use gvimdiff in windows?
If I already have a gvim window open how do I launch a new separate
instance of gvim from inside the first window (without having to go to
the desktop and click the icon!)
Sorry this is more of a windows question than gvim: On my linux machine
running KDE I have Ctrl-Shift-G set up to launch gvim, is there a way to
set a keyboard shortcut in Windows XP to do the same?
Many thanks for any help,
Rob.
if diff
set lines=999 columns=999
else
set lines=80 columns=88
endif
Notes:
1. This doesn't work in Tiny-version vim, which treats everything from
:if to :endif as a (recursive) comment.
2. This won't work, of course, when running console Vim in a
non-resizable console. If you don't want to ever try resizing a console
Vim, you may either wrap it all within :if has('gui_running') or move
it to your gvimrc .
3. This won't work when setting diff mode after starting Vim.
Best regards,
Tony.
Mac OS 10.3 - v7.0 - netrwPlugin.vim
Hello, 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. So I changed the name of netrwPlugin.vim to stop it and pasted the old explorer.vim into my plugin directory. I don't have the time nor the expertise to go through the netrwPlugin.vim to see if I will be breaking anything I might really need. I couldn't find anything in :help about it, nor on the vim site or the authors site. Any thoughts? Thanks, dstefani
RE: Visible Spaces
Would you be satisfied with changing the background color for
spaces? Step 1:
Ah, that's an idea. Just / to search for spaces (assumes
highlighting's turned on), and they'll all be highlighted. He wants to
turn off highlighting, just /qqq or something.
Else maybe tweak the font to change space to middot; or something.
Thing is, change the font to something else, and that goes away, and
he'd have to tweak the font for that as well.
Eg, if he's using Lucida console 10pt, make a copy of the font, rename
to something else (Lucidaspace or whatever), edit the font to change
the space char, then when you want visispaces, just font your way to
that. Want invisispaces again, change back to the normal Lucida font.
I prefer /;; to turn off highlighting. the keys are right next to each
other and never happen in any languages I use.
For spaces, maybe not exactly the same thing, but I have a .vim to color
every three out of four leading spaces as magenta underline (in a
non-expandtab file). The file also points out a lot of other spacing issues.
Activate this anywhere that doesn't have a strict real-tab rule and
you'll see all the inconsistancies light up. The blue underlines
between words are ok and just there to help line up widely spaced tables.
I should probably add something to ignore the two spaces between
sentences in prose.
odd_space.vim:
syn match newtab [\t]\+$ containedin=ALL
syn match spacereturn [ ]$ containedin=ALL
syn match spacetab[ ]\tme=e-1 containedin=ALL
syn match tabspace\t[ ]\+lc=1 containedin=ALL
syn match tabtab [ -'*-Z^-z|~]\t\t\t*[
-'*-.0-Z^-z|~]lc=1,me=e-1
containedin=ALLBUT,cComment
syn match leadspace [ ][ ]lc=1 contained
syn match pairspace [ ][ ]hs=s+1 contained
nextgroup=pairspace,leadspace
syn match quadspace [ ][ ][ ][ ]hs=s+1 contained
nextgroup=quadspace,pairspace,leadspace
syn match pairstart ^[ ][ ]hs=s+1
nextgroup=quadspace,pairspace,leadspace
syn match quadstart ^[ ][ ][ ][ ]hs=s+1
nextgroup=quadspace,pairspace,leadspace
syn match spaces [^ ][ ]\{2,}lc=1
hi spacetab ctermfg=Red guifg=red
gui=underline cterm=underline
hi tabspace ctermfg=Red guifg=red
gui=underline cterm=underline
hi spacereturn ctermfg=Red guifg=red
gui=underline cterm=underline
hi newtab ctermfg=Blueguifg=#FF gui=underline
cterm=underline
hi tabtab ctermfg=Blueguifg=#88 gui=underline
cterm=underline
if expandtab == 0
hi quadspacectermfg=Magenta guifg=#440044 gui=underline
cterm=underline
else
hi link quadspace Normal
endif
hi linkpairstart pairspace
hi linkquadstart quadspace
hi spaces ctermfg=DarkRed guifg=#55 gui=underline
cterm=underline
hi pairspacectermfg=Yellow guifg=#00 gui=underline
cterm=underline
hi link leadspace pairspace
--
_
( \ _ \/_ / _ _ Jason Weber Glendale, CA
\|(\/)())) \/\/(-/_)(-/( http://www.imonk.com/baboon [EMAIL PROTECTED]
// [EMAIL PROTECTED]
(/
Re: Visible Spaces
Jason Weber wrote: Would you be satisfied with changing the background color for spaces? Step 1: Ah, that's an idea. Just / to search for spaces (assumes highlighting's turned on), and they'll all be highlighted. He wants to turn off highlighting, just /qqq or something. Else maybe tweak the font to change space to middot; or something. Thing is, change the font to something else, and that goes away, and he'd have to tweak the font for that as well. Eg, if he's using Lucida console 10pt, make a copy of the font, rename to something else (Lucidaspace or whatever), edit the font to change the space char, then when you want visispaces, just font your way to that. Want invisispaces again, change back to the normal Lucida font. I prefer /;; to turn off highlighting. the keys are right next to each other and never happen in any languages I use. [...] To turn off highlighting until next search, vim has the :noh[lsearch] command. You may want to use something like :map ;; :nohCR if :noh (4 keys including Enter) is too long for you. Best regards, Tony.
Re: Visible Spaces
On Fri 21-Jul-06 12:51pm -0600, Jason Weber wrote: Ah, that's an idea. Just / to search for spaces (assumes highlighting's turned on), and they'll all be highlighted. He wants to turn off highlighting, just /qqq or something. I prefer /;; to turn off highlighting. the keys are right next to each other and never happen in any languages I use. I clear the last search pattern often enough that I use a mapping: map leader\ :let @/=barecho Search pattern clearedcr -- Best regards, Bill
Other European languages on a US keyboard
I sometimes need to write text in other languages such as French, Spanish and occasionally German or Italian. I would like to do this in Vim. Unfortunately I only have a US keyboard. Using Ctrl-K to enter the various digraphs becomes somewhat cumbersome for anything larger than a short paragraph. Unfortunately I am only able to type the US keyboard, so remapping the keyboard might be a better solution than entering digraphs in the long run but will not be painless.. And since I do not do this on a regular basis, I am unsure whether it's really worth going to all the trouble. I was thinking of writing the text without accents, tildes, cedillas, etc. using the letters on the US keyboard and then feeding the result to some advanced functionality of a spellchecker that would replace all the words that can only be spelled one way by their correctly spelled version - say French 'épeler (to spell) can only be spelled this way.. there is no 'epeler' or 'èpeler' or 'êpeler'. On the other hand, for those words where the accent differs depending on the semantics such as French 'a' vs. 'à', the script/plugin would leave them untouched and - ideally - highlight them, thus leaving me with only a handful of manual corrections. Is there anything in Vim that does something like this? Or is there any other 'smart' way to achieve something like the above? Thanks cga
Re: Visible Spaces
From: Bill McCarthy, Jul 21, 2006 2:14 PM I clear the last search pattern often enough that I use a mapping: map leader\ :let @/=barecho Search pattern clearedcr Which does the same as: :noh -- Steve Hall [ digitect dancingpaper com ]
Re: user defined command n/a in Tiny mode, any has() +xxx reqired for that?
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Use if 1 | endif to wrap everything is possible, but not always, since the script may use finish to terminate itself and attach some data after the finish. In the Tiny version the finish is not possible, so the script will execute into the data and got thousands of errors. You can try --- ~/.vimrc -- if 1 skipped on tiny vim source ~/.vimrc-full skipped on tiny finish skipped on tiny endif source ~/.vimrc-tiny --- or - ~/.vimrc - source ~/.vimrc-tiny if 1 skipped on tiny source ~/.vimrc-full skipped on tiny endif skipped on tiny Yakov
RE: Other European languages on a US keyboard
Unfortunately I am only able to type the US keyboard, so remapping the keyboard might be a better solution than entering digraphs in the long run but will not be painless.. And since I do not do this on a regular basis, I am unsure whether it's really worth going to all the trouble. Would it be impractical to map, eg, ^e to whatever the code is for 'ê', ie, use prefix notation of [^'`~,], etc., as a prefix for [aeioucnAEIOUCN] as needed? Wouldn't be *all* those combinations, but, eg, would only need ,C for Ccedil;, ~N for Ntilde; (and their lowercase counterparts, natch), but the rest would just be whatever accented chars you normally use, for grave, acute, circumflex, etc. I'm not sure how a non-US keyboard does such things, so I can't suggest a more transparent way of doing it. One other possibility would be the way my phone does multiple chars per key, eg, you'd hit '1' to get the generic '.', then '*' would cycle through different punctuation, and so on, 'til it'd get back to '.' again. Maybe hitting alt-A would get you an 'a' and put you into a loop, then multiple hits of an F-key would cycle through the 3-4 other chars and then back. Any other key would escape the loop. Arrange them in the order you expect their occurrence, most commonly-used ones first. Eg, if you arrange them in the order acute/grave/circumflex/ring, simply hitting M-a would get you aacute;. Hit F2, and it gets you agrave;. Hit F2 again, circumflex. Again, ring. Again, acute. Lather, rinse, repeat. *Implementing* this would for now be beyond my ken, or my barbie, but I'm sure someone might have some ideas how to best do it. No?
Re: Visible Spaces
On Fri 21-Jul-06 1:36pm -0600, Steve Hall wrote: From: Bill McCarthy, Jul 21, 2006 2:14 PM I clear the last search pattern often enough that I use a mapping: map leader\ :let @/=barecho Search pattern clearedcr Which does the same as: :noh They do produce the same immediate visual affect. They are not the same. :noh leaves the search pattern active. After ':noh' try 'n' to see the highlighting back on. let @/= replaces the last search pattern with an empty string. Typing 'n' will produce this message: E35: No previous regular expression -- Best regards, Bill
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. I would like to do this in Vim. Unfortunately I only have a US keyboard. Using Ctrl-K to enter the various digraphs becomes somewhat cumbersome for anything larger than a short paragraph. Unfortunately I am only able to type the US keyboard, so remapping the keyboard might be a better solution than entering digraphs in the long run but will not be painless.. And since I do not do this on a regular basis, I am unsure whether it's really worth going to all the trouble. I was thinking of writing the text without accents, tildes, cedillas, etc. using the letters on the US keyboard and then feeding the result to some advanced functionality of a spellchecker that would replace all the words that can only be spelled one way by their correctly spelled version - say French 'épeler (to spell) can only be spelled this way.. there is no 'epeler' or 'èpeler' or 'êpeler'. On the other hand, for those words where the accent differs depending on the semantics such as French 'a' vs. 'à', the script/plugin would leave them untouched and - ideally - highlight them, thus leaving me with only a handful of manual corrections. Is there anything in Vim that does something like this? Or is there any other 'smart' way to achieve something like the above? Thanks cga I. Since you've already used digraphs, and they're too cumbersome for you, you could try a keymap. There are some keymaps in $VIMRUNTIME/keymap which you can apply by just doing :setlocal keymap=keymapname (where keymapname is the filename without the encoding and .vim endings) or by using the Edit - Keymap menu. Then you can toggle between US-QWERTY mode and keymap mode by hitting Ctrl-^ in Insert mode, or by toggling 'iminsert' between zero and 1 in any mode. Basically, what a keymap does is establish a set of language-mappings, i.e., insert-mode mappings which can be turned on an off. Try the accents keymap, it might be just what you want. 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. You might want to write something more extensive but this will show you how to do it. If and when you write your own keymap, place it in the keymap/ subdirectory of a directory listed early in 'runtimepath' but not in $VIMRUNTIME/keymap itself because any upgrade can silently change anything there. II. What you are suggesting looks like setting 'spelllang' (with three ells) to whatever means French and then spellchecking your US-ASCII-only text. But beware: the Vim spellchecker (which I don't use because of my good innate spelling) might not be clever enough to mark words which have accented homographs, such as a (has) vs. à (at), de (of) vs. dé (thimble), du (of the) vs. dû (owed), cru (believed or raw) vs. crû (grown) etc.: so the cure might be worse than the ill, owing to the necessity of looking for unmarked spelling mistakes even after running the spell checker. Best regards, Tony.
Re: Perl::Tags (Was: perlcomplete.vim -- anyone working on this?
Have you got PERL5LIB set to look in lib/ and t/ ?
Module::Locate defaults to looking at @INC.
You could set this in your environment variables.
Of course, it would be nice if Perl::Tags would look at:
use lib qw( );
declarations and add those to where it looks for modules...
By the way, Dr Bean, if you'd like commit access to the
repo at http://greenokapi.net/svn/code/Perl-Tags/ just
email me the output of htpasswd and I'll add to the
auth file :-)
--
osfameron
On 21/07/06, Dr Bean [EMAIL PROTECTED] wrote:
On Wed, 12 Jul 2006, Dr Bean wrote:
On Wed, 12 Jul 2006, Hakim Cassimally wrote:
Also... at the moment the script in the manpage doesn't have a mapping
to refresh the tags file. If you defined the sub after opening the
file, it won't be seen until you close and reopen. (I'll probably fix
this soon, but patches welcome :-)
Making s:do_tags a global function, Do_tags allows you to call it
yourself, call Do_tags(expand('%')).
I don't understand why this doesn't work when you source
perl.vim.
This autocommand refreshes the tags file when you write, but the
tags you have last written are the last ones you want to jump
to, so I don't think it is much use.
augroup perltags
au!
autocmd BufWritePost *.pm,*.pl call s:do_tags(expand('%'))
augroup END
I am more worried that Module::Locate doesn't find modules in lib/ and t/
--
Dr Bean You can lead a horse to water,
but you can't make it drink
unless you gallop it round first.
Re: Other European languages on a US keyboard
On 7/21/06, cga2000 [EMAIL PROTECTED] wrote: I sometimes need to write text in other languages such as French, Spanish and occasionally German or Italian. I would like to do this in Vim. Unfortunately I only have a US keyboard. Using Ctrl-K to enter the various digraphs becomes somewhat cumbersome for anything larger than a short paragraph. Unfortunately I am only able to type the US keyboard, so remapping the keyboard might be a better solution than entering digraphs in the long run but will not be painless.. And since I do not do this on a regular basis, I am unsure whether it's really worth going to all the trouble. I was thinking of writing the text without accents, tildes, cedillas, etc. using the letters on the US keyboard and then feeding the result to some advanced functionality of a spellchecker that would replace all the words that can only be spelled one way by their correctly spelled version - say French 'épeler (to spell) can only be spelled this way.. there is no 'epeler' or 'èpeler' or 'êpeler'. On the other hand, for those words where the accent differs depending on the semantics such as French 'a' vs. 'à', the script/plugin would leave them untouched and - ideally - highlight them, thus leaving me with only a handful of manual corrections. Is there anything in Vim that does something like this? Or is there any other 'smart' way to achieve something like the above? I think the easiest apporach is to craete mappings. You could use ctrl-(a-z), ctrl-shift(a-z), ctrl-alt-(a-z), then f1-f12 + ctrl/alt/del combinations. Linux has a keyboard mode where ' is used to modify letters to create diactitics. This works for all X applications, not just vim. Yakov
