Antony Scriven schrieb:
Hi all. I've often encountered the situation where a plugin
maps keys that I've wistfully mapped in my vimrc. I think it
would be useful for a user to be able to prevent this, say
by using a notation such as
:map final \x foo
Then if Vim tries to map \x
Yakov Lerner wrote:
On Fri, May 23, 2008 at 7:54 PM, Philippe Fremy [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Tony Mechelynck wrote:
On 22/05/08 15:52, Philippe Fremy wrote:
[...]
The conclusion seems pretty clear: mapping code is not executed when
Try this:
vim --remote-expr 'feedkeys(\F4)'
:help feedkeys()
Thanks. It works, but it is not portable, so that's not enough for me.
But anyway, I can go without mapping support in --remote-send, if I am
aware of it.
Not portable?! Why not?
Ben.
Bram Moolenaar wrote:
Philippe Fremy wrote:
I've noticed that after applying setModified through the netbeans
interface, the tab bar, status bar and title are not updated to reflect
the changed modified status.
The proposed patch fixes that. I am a beginner in vim development, so
tell
Ben Schmidt wrote:
Try this:
vim --remote-expr 'feedkeys(\F4)'
:help feedkeys()
Thanks. It works, but it is not portable, so that's not enough for me.
But anyway, I can go without mapping support in --remote-send, if I am
aware of it.
Not portable?! Why not?
My mistake, I checked
2008/5/28 Andy Wokula [EMAIL PROTECTED]:
Antony Scriven schrieb:
Hi all. I've often encountered the situation where a plugin
maps keys that I've wistfully mapped in my vimrc. I think it
would be useful for a user to be able to prevent this, say
by using a notation such as
2007/5/28 Nikolai Weibull [EMAIL PROTECTED]:
On Wed, May 28, 2008 at 12:04 PM, Nikolai Weibull [EMAIL PROTECTED] wrote:
On Wed, May 28, 2008 at 1:37 AM, Antony Scriven
[EMAIL PROTECTED] wrote:
Hi all. I've often encountered the situation where a plugin
maps keys that I've
On Wed, May 28, 2008 at 1:37 AM, Antony Scriven [EMAIL PROTECTED] wrote:
Hi all. I've often encountered the situation where a plugin
maps keys that I've wistfully mapped in my vimrc. I think it
would be useful for a user to be able to prevent this, say
by using a notation such as
:map
The way it stands right now a user cannot
prevent a plugin writer from overwriting their maps.
Yes they can, as detailed by a previous poster, using autocommands or after
scripts the user can have the last say.
There is also the solution most of us use for Emacs. The user can choose not to
Philippe Fremy wrote:
I've noticed that after applying setModified through the netbeans
interface, the tab bar, status bar and title are not updated to reflect
the changed modified status.
The proposed patch fixes that. I am a beginner in vim development, so
tell me if it's not the
On May 27, 4:37 pm, James Widman [EMAIL PROTECTED] wrote:
On 2008/05/27, at 15:49, François Ingelrest wrote:
While I totally dislike putting preprocessor directives in the first
column, I doubt this will be changed as this could break
compatibility with previous versions.
Patch 7.1.299
Problem:Filetype detection doesn't work properly for file names ending in
a part that is ignored and contain a space or other special
characters.
Solution: Escape the special characters using the new fnameescape function.
Files:
With current versions of gvim (such as 7.1.298), composing characters
are displayed one character cell left of where they ought to be. See the
discussion (initially about Thai text) between Nwngz and me in the
vim_use group for details.
The problem has been seen on both Windows and Linux/GTK2
2008/5/28 Tony Mechelynck [EMAIL PROTECTED]:
[...]
You could even use
: au VimEnter * au FileType * map buffer {lhs} {rhs}
Thanks. I think I'll have to resort to this, but with a longer
list of autocommands: I don't appear to be garnering much
support! I still think it's
Patch 7.1.301
Problem:When the File/Save menu is used in Insert mode, a tab page label
is not updated to remove the +.
Solution: Call draw_tabline() from showruler(). (Bjorn Winckler)
Files: src/screen.c
*** ../vim-7.1.300/src/screen.c Sun Mar 9 14:30:12 2008
---
On 5/28/08, Erik Falor [EMAIL PROTECTED] wrote:
On 5/28/08, Meikel Brandmeyer [EMAIL PROTECTED] wrote:
Hello,
No worries, but I'd argue that they are not solutions since
they aren't currently working for me. I don't think the user
should be penalised if a plugin writer doesn't check
Hi!
I have fetched the newest version from CVS and get the following errors:
ex_getln.c: In function `ExpandEscape':
ex_getln.c:3659: error: structure has no member named `xp_shell'
ex_getln.c: In function `vim_strsave_fnameescape':
ex_getln.c:3712: error: `p' undeclared (first use in this
Patch 7.1.302 (after 7.1.299)
Problem:Compilation error on MS-Windows.
Solution: Don't use xp_shell when it's not defined.
Files: src/ex_getln.c
*** ../vim-7.1.301/src/ex_getln.c Wed May 28 22:01:46 2008
--- src/ex_getln.c Wed May 28 22:01:48 2008
***
***
Georg Dahn wrote:
I have fetched the newest version from CVS and get the following errors:
ex_getln.c: In function `ExpandEscape':
ex_getln.c:3659: error: structure has no member named `xp_shell'
ex_getln.c: In function `vim_strsave_fnameescape':
ex_getln.c:3712: error: `p' undeclared
From: Patrick Texier, Wed, May 28, 2008 5:38 pm
Le Wed, 28 May 2008 22:02:26 +0200, Bram Moolenaar a écrit dans le
message :
Patch 7.1.302 (after 7.1.299)
Problem: Compilation error on MS-Windows.
Solution: Don't use xp_shell when it's not defined.
Files: src/ex_getln.c
On 28/05/08 17:46, Antony Scriven wrote:
2008/5/28 Tony Mechelynck[EMAIL PROTECTED]:
[...]
You could even use
: au VimEnter * au FileType * mapbuffer {lhs} {rhs}
Thanks. I think I'll have to resort to this, but with a longer
list of autocommands: I don't
21 matches
Mail list logo
