On Sep 16, Maxim Kim wrote:
> среда, 16 сентября 2020 г. в 03:38:37 UTC+3, Antony Scriven:
>
> > In case I wasn't clear before, I'm wondering if could you save sg_link
> > > in do_highlight() when doing ":hi def link", and then restore it in
&g
>
> In case I wasn't clear before, I'm wondering if could you save sg_link
> in do_highlight() when doing ":hi def link", and then restore it in
> highlight_clear(). Or would there be unintended consequences?
>
> I've not had any highlighting issues since trying it out (altering links
> and then
Hey folks. There's something up with mappings. I noticed this patch:
3885 8.1.2159 some mappings are listed twice
but there's still an issue somewhere.
gVim 8.2, Win32, via installer.
gvim -u NONE -N
:map ^N x| "literal Ctrl-N character
:unmap
E31: No such mapping
Though
Hi!
> Solution: Only use the "extends" character when 'list' is on. (Hirohito
> Higashi, closes #4360)
This change may be consistent, but is it helpful?
It seems to me that extends and precedes provide basic UI
feedback akin to a scrollbar or the 'display' option, rather
than
Hi, I wonder if ":h jump-motions" needs updating.
Some jump commands that aren't mentioned:
:p :#
:cn etc.
gd etc.
u
* #
[count]zz etc.
zj etc.
:goto
Any movement under :g
I don't know if that's an exhaustive list, or if some of those
are considered to be
Hi folks.
:let List = {x -> [x]}
:let Extract = {-> function(g:List, [3])()[0]}
gives: 'E695: Cannot index a Funcref'. Whereas
:echo function(g:List, [3])()[0]
is fine.
Is this expected behaviour in a lambda?
--Antony
--
--
You received this message from the "vim_dev"
On 2 November 2016 at 16:51, Coacher wrote:
> [...] Consider the following file:
>
> \begin{env}
>
x
x
> \end{env}
>
> Open it like this: vim -N
On 14 March 2010 13:53, mobi phil m...@mobiphil.com wrote:
I think it would make enough sense to extend the
textobjects with af that would select a function,
[...]
Define 'a function'. --Antony
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
On 1 March 2010 14:54, Ben Fritz fritzophre...@gmail.com wrote:
On Feb 26, 1:41 am, winterTTr winterttr@gmail.com wrote:
the Code like below( just an example, not the real code ):
I am trying to use the set eventignore+=BufEnter and set
eventignore-=BufEnter to prevent the
I vaguely wrote:
[...]
Me too. It looks to me like 'ei' is being set to
,Syntax which is causing do_set() to fail
... on a subsequent :set ei+=.
I hope that's clearer. --Antony
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
On Sat, Jan 17, 2009 at 12:56 PM, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 17/01/09 09:48, Dominique Pelle wrote:
Benjamin Fritz wrote
A patch is attached for the behavior discussed in
these threads:
Hi
2008/12/17 David Fishburn dfishburn@gmail.com:
On Wed, Dec 17, 2008 at 10:40 AM, Ben Fritz fritzophre...@gmail.com wrote:
On Dec 17, 6:46 am, Ben Schmidt mail_ben_schm...@yahoo.com.au wrote:
...
The other problem I saw with not using the fold column
was the fact that URLs
Hi
2008/12/1 Ron Aaron [EMAIL PROTECTED]:
[...]
sql_exec( {handle}, {sql} [, {separator}] ) *sql_exec()*
Execute the SQL (a string of valid SQL commands) on the
opened {handle}, which must have been returned from
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
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
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
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 elsewhere, the command is ignored.
Nico Weber [EMAIL PROTECTED] wrote:
[...]
the GUI version and that's the way GUIs generally look
like. The same goes for icons in notebook tabs: Almost
all the GUI applications I can think of display such an
icon although the label would be sufficient. It's just
a bit nicer
2008/5/6 Antony Scriven [EMAIL PROTECTED]:
[... about icons for filetypes in GUI tabs ...]
But... Vim can detect ~500 different filetypes. Who's
coming up with 500 distinct and easily recognizable
icons? --Antony
Btw, I didn't mean for that to sound negative. I'd be happy
if you could
On 17/04/2008, Gary Johnson [EMAIL PROTECTED] wrote:
On 2008-04-17, A.Politz [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Vimmers,
i'm patched through 293 and running suse started vim
with vim -u NONE -U NONE
to produce the weirdness start vim and set incsearch
On 09/04/2008, Bram Moolenaar [EMAIL PROTECTED] wrote:
Antony Scriven wrote:
On 08/04/2008, Bram Moolenaar [EMAIL PROTECTED] wrote:
I have been preparing a talk for the upcoming FISL
conference in Brazil:
http://fisl.softwarelivre.org/9.0/www/
One
On 08/04/2008, Bram Moolenaar [EMAIL PROTECTED] wrote:
I have been preparing a talk for the upcoming FISL
conference in Brazil:
http://fisl.softwarelivre.org/9.0/www/
One of the items I planned to discuss is why Vim has no
floating point support. Well, this turned into actually
On 03/04/2008, char101 [EMAIL PROTECTED] wrote:
On Apr 1, 3:53 pm, Xiaozhou Liu [EMAIL PROTECTED] wrote:
[...]
The patch does not work with Visual C++ 9.0 2008. The
main problem is this macros
+#define PUSH(s){ \
+ if
On 28/03/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
[...]
Jeffrey Friedel discusses this in his book Mastering
Regular Expressions in chapter 4, section NFA, DFA, and
POSIX. [...] Jeffrey writes: If efficiency
is an issue with a Traditional NFA (and with
backtracking, believe
On 26/03/2008, Xiaozhou Liu [EMAIL PROTECTED] wrote:
Hi Vimmers,
During the development of the new regexp, one thing
confuses me a lot: ordered alternation. (e.g. given r.e.
'ab\|abc' and text 'abc', 'ab' matched, not 'abc')
I know that 100% compatibility is one of the project
On 27/03/2008, Ben Schmidt [EMAIL PROTECTED] wrote:
Antony Scriven wrote:
[...]
[...] I'd prefer the longest match rather than the
first alternative (as specified by POSIX) [...]
An interesting twist. Can you clarify which behaviour
POSIX specifies (your sentence above
On 27/03/2008, Nikolai Weibull [EMAIL PROTECTED] wrote:
On Thu, Mar 27, 2008 at 1:16 PM, Antony Scriven
[EMAIL PROTECTED] wrote:
On 27/03/2008, Ben Schmidt [EMAIL PROTECTED] wrote:
Antony Scriven wrote:
I'd prefer the longest match rather than the
first alternative
On 15/08/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Hello!
I'd like to do
imap ... = ...=c-o:somethingcr
however, . no longer repeats the small change. For example:
imap = =c-o:echo hello!cr
work with the following file contents:
abc;
def;
Place
Hi all. I have a working proof-of-concept (i.e. it's
currently a mess) of recursive :globals. Some examples.
To replace `bar' with `baz' if it's on a line immediately
preceding `foo' use
:g/foo/ -g/bar/ s//baz/
or alternatively
:g/bar/ k m | +g/foo/ 'm s/bar/baz/
With the following in
Hi
Vim crashes with
$ vim -u NONE
Qa
^T0^D^D.
Also
Qa
^D^D^D^D
will result in all the `0's being deleted. I reckon only the
last one should be, that a `0' typed only immediately before
a ^D should have an effect. I just made that up :-) Vi does
this only immediately after
30 matches
Mail list logo
