On 14 October 2017, Kazunobu Kuriyama wrote:
> 2017-10-13 23:54 GMT+09:00 LCD 47 :
>
> > On 13 October 2017, Kazunobu Kuriyama
> > wrote:
> > > 2017-10-13 23:24 GMT+09:00 LCD 47 :
> > > > "man-db", which is a "man" implem
On 13 October 2017, Kazunobu Kuriyama
wrote:
> 2017-10-13 23:24 GMT+09:00 LCD 47 :
> > "man-db", which is a "man" implementation used on some Linux
> > distributions, sets the environment variable MAN_PN to something
> > like "ls(1)", an
On 13 October 2017, Kazunobu Kuriyama
wrote:
> 2017-10-13 22:25 GMT+09:00 LCD 47 :
[...]
> > I don't think the MANPAGER way can be salvaged without MAN_PN
> > (i.e. the problem of "man Xorg" and "man Net::DNS" can't be solved
> > reasonably w
On 13 October 2017, Christian Brabandt wrote:
>
> On Fr, 13 Okt 2017, LCD 47 wrote:
>
> > It isn't that I don't _like_ it. Your patch changes the
> > non-MAN_PN branch, it's unrelated to mine. As I said, I'm
> > suggesting the wrappe
On 13 October 2017, Kazunobu Kuriyama
wrote:
> 2017-10-13 21:04 GMT+09:00 LCD 47 :
>
> > On 13 October 2017, Kazunobu Kuriyama
> > wrote:
> > > HI,
> > >
> > > To get your patch to work for macOS, I needed to add some tweaks
> > > to that.
On 13 October 2017, Kazunobu Kuriyama wrote:
> HI,
>
> To get your patch to work for macOS, I needed to add some tweaks to that.
> Please find the attached patch and consider merging it into yours. Of
> course, it's fine to me that you reject or modify it freely; I leave that
> to you.
>
> Mor
On 12 October 2017, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 10 October 2017, LCD 47 wrote:
> > > On 10 October 2017, Bram Moolenaar wrote:
> > > >
> > > > lcd wrote:
> > > >
> > > > > Per title: if MANPAGE
On 10 October 2017, LCD 47 wrote:
> On 10 October 2017, Bram Moolenaar wrote:
> >
> > lcd wrote:
> >
> > > Per title: if MANPAGER is set to "env MAN_PN=1 vim -M +MANPAGER -",
> > > running "man Xorg" results in a message "Ca
On 10 October 2017, Bram Moolenaar wrote:
>
> lcd wrote:
>
> > Per title: if MANPAGER is set to "env MAN_PN=1 vim -M +MANPAGER -",
> > running "man Xorg" results in a message "Cannot find a 'xorg'.".
> >
> > The culprit is a "tolower()" in plugin/manpager.vim. Man page names
> > are ca
On 10 October 2017, LCD 47 wrote:
> Per title: if MANPAGER is set to "env MAN_PN=1 vim -M +MANPAGER -",
> running "man Xorg" results in a message "Cannot find a 'xorg'.".
>
> The culprit is a "tolower()" in plugin/manpager.
On OpenBSD the argument for the man pager is always passed as a
file. This means the environment variable MANPAGER has to be adjusted
like this:
export MANPAGER="env MAN_PN=1 vim -M +MANPAGER"
I haven't checked the sources for unexpected side effects, but it
seems to work.
/
Per title: if MANPAGER is set to "env MAN_PN=1 vim -M +MANPAGER -",
running "man Xorg" results in a message "Cannot find a 'xorg'.".
The culprit is a "tolower()" in plugin/manpager.vim. Man page names
are case-sensitive on most UNIX systems. The patch below seems to fix
the problem.
On 31 August 2017, Yegappan Lakshmanan wrote:
> Hi,
>
> On Thu, Aug 31, 2017 at 9:02 AM, LCD 47 wrote:
> > On 27 August 2017, Bram Moolenaar wrote:
> >>
> >> Patch 8.0.1006
> >> Problem:Cannot parse text with 'erroformat' without chan
On 27 August 2017, Bram Moolenaar wrote:
>
> Patch 8.0.1006
> Problem:Cannot parse text with 'erroformat' without changing a quickfix
> list.
> Solution: Add the "text" argument to getqflist(). (Yegappan Lakshmanan)
> Files: runtime/doc/eval.txt, src/evalfunc.c, src/proto/q
On 3 August 2017, Christian Brabandt wrote:
>
> On Do, 03 Aug 2017, Bram Moolenaar wrote:
>
> >
> > I wrote:
> >
> > > Christian wrote:
> > >
> > > > as requested in #1665 (distribute more colorschemes with Vim). Here is
> > > > the seoul256 colorscheme. The author explicitly gives permissio
On 20 July 2017, Yegappan Lakshmanan wrote:
> Hi,
>
> On Thu, Jul 20, 2017 at 6:59 AM, Yegappan Lakshmanan
> wrote:
> > Hi,
> >
> > I am investigating a memory leak reported by valgrind with this
> > patch.
> >
>
> I am attaching an updated patch with the fix for this memory leak and
> additional
On 2 July 2017, Yegappan Lakshmanan wrote:
> Hi,
>
> On Sun, Jul 2, 2017 at 12:11 PM, LCD 47 wrote:
> >> >>
> >> >> When one plugin is asynchronously updating a quickfix list,
> >> >> currently it is not possible for another plugin to
On 2 July 2017, Yegappan Lakshmanan wrote:
> Hi,
>
> On Sun, Jul 2, 2017 at 6:45 AM, LCD 47 wrote:
> > On 1 July 2017, Yegappan Lakshmanan wrote:
> >> Hi all,
> >>
> >> When one plugin is asynchronously updating a quickfix list,
> >> curren
On 1 July 2017, Yegappan Lakshmanan wrote:
> Hi all,
>
> When one plugin is asynchronously updating a quickfix list, currently it
> is not possible for another plugin to update another quickfix list
> synchronously or asynchronously using the cexpr, cfile, and other
> commands. The setqflist() f
On 20 April 2017, Yegappan Lakshmanan wrote:
> Hi,
>
> On Wed, Apr 19, 2017 at 4:23 PM, Daniel Hahler
> wrote:
> > It might also be possible to allow for setting valid?!
> >
> > Are you referring to changing the setqflist() function to accept the
> > valid flag field and not checking for a valid
Today I stumbled upon this article about JSON:
http://seriot.ch/parsing_json.php
The article links to a set of tests:
https://github.com/nst/JSONTestSuite
A quick run of the "y" and "n" tests against Vim's json_decode()
finds a few problems. Not particularly ground-
Pretty much self-explanatory.
/lcd
diff --git a/runtime/doc/windows.txt b/runtime/doc/windows.txt
index 0ef1a8b..ba0075d 100644
--- a/runtime/doc/windows.txt
+++ b/runtime/doc/windows.txt
@@ -295,8 +295,8 @@ CTRL-W CTRL-Q
*CTRL-W_CTRL-Q*
On 14 October 2016, Bram Moolenaar wrote:
>
> Ozaki Kiichi wrote:
>
> > Currently, vim checks ended-job every 10 second; thus exit_cb is delayed
> > 10 seconds at the maximum.
> >
> > I propose the following:
> >
> > https://gist.github.com/ichizok/fe9743f46822a9015ed2f7d65238c5db
> >
> > os_
On 8 October 2016, Bram Moolenaar wrote:
>
> > Lcd wrote:
> >
> > On 7 October 2016, Gerd Wachsmuth wrote:
> > > > The issue is that the multiline error is started by %W and ends with %Z
> > > > without adding any errors.
> > > In my opinion, it is not the issue that no `%C` is present:
> > >
On 7 October 2016, Gerd Wachsmuth wrote:
> > The issue is that the multiline error is started by %W and ends with %Z
> > without adding any errors.
> In my opinion, it is not the issue that no `%C` is present:
> With
>
> set efm=%+Eerror\ %l,%-Winfo\ %m\ %l,%+Ceven\ more\ %m,%Zmore\ info
> (
On 27 September 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Fri, Sep 16, 2016 at 11:32 PM, LCD 47 wrote:
> > On 16 September 2016, Yegappan Lakshmanan wrote:
> >> Hi,
> >>
> >> On Sun, Sep 11, 2016 at 4:08 AM, LCD 47 wrote:
>
On 23 September 2016, Christian Brabandt wrote:
> Hi Markus!
>
> On Fr, 23 Sep 2016, Markus Knecht wrote:
>
> > Thanks, matchaddops seems to be exactly the functionality i need,
> > sadly I get a failure that the function matchaddpos is unknown,
> > probably I'm missing something obvious
>
> Y
On 21 September 2016, Markus Knecht wrote:
> Hello,
>
> For a project I have to import some markings into vim and for that I'm
> writing a plugin. These markings are in the form of:
> line start,
> coloumn start, //the start character index
> line end,
> coloumn end, //the end character
On 16 September 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Sun, Sep 11, 2016 at 4:08 AM, LCD 47 wrote:
> > On 12 August 2016, Bram Moolenaar wrote:
> >>
> >> Patch 7.4.2200
> >> Problem:Cannot get all information about a quickfix list.
> &
On 12 September 2016, Bram Moolenaar wrote:
>
>
> Hello Vim users!
>
>
> Announcing: Vim (Vi IMproved) version 8.0
[...]
Congratulations!
/lcd
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mor
On 11 September 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 12 August 2016, Bram Moolenaar wrote:
> > >
> > > Patch 7.4.2200
> > > Problem:Cannot get all information about a quickfix list.
> > > Solution: Add an optional argument to get/set loc/qf list(). (Yegappan
> > >
On 12 August 2016, Bram Moolenaar wrote:
>
> Patch 7.4.2200
> Problem:Cannot get all information about a quickfix list.
> Solution: Add an optional argument to get/set loc/qf list(). (Yegappan
> Lakshmanan)
[...]
> + If the optional {what} dictionary argument is supp
On 3 September 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > > > On 1 September 2016, Bram Moolenaar wrote:
> > > > >
> > > > > Patch 7.4.2299 Problem: QuickFixCmdPre and QuickFixCmdPost
> > > > > autocommands are not always triggered. Solution: Also
> > > > > trigger on ":expr", ":cbuffer"
On 2 September 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 1 September 2016, Bram Moolenaar wrote:
> > >
> > > Patch 7.4.2299 Problem: QuickFixCmdPre and QuickFixCmdPost
> > > autocommands are not always triggered. Solution: Also trigger
> > > on ":expr", ":cbuffer", etc. (Yegappan Lak
On 2 September 2016, Christian Brabandt wrote:
> Hi LCD!
>
> On Fr, 02 Sep 2016, LCD 47 wrote:
>
> > On 2 September 2016, Ingo Karkat wrote:
> > > On 09/02/2016 09:51 PM, LCD 47 wrote:
> > > > On 1 September 2016, Bram Moolenaar wrote:
> > > >
On 2 September 2016, LCD 47 wrote:
> On 2 September 2016, Ingo Karkat wrote:
> > On 09/02/2016 09:51 PM, LCD 47 wrote:
> > > On 1 September 2016, Bram Moolenaar wrote:
> > >>
> > >> Patch 7.4.2299 Problem: QuickFixCmdPre and QuickFixCmdPost
&g
On 2 September 2016, Ingo Karkat wrote:
> On 09/02/2016 09:51 PM, LCD 47 wrote:
> > On 1 September 2016, Bram Moolenaar wrote:
> >>
> >> Patch 7.4.2299 Problem: QuickFixCmdPre and QuickFixCmdPost
> >> autocommands are not always triggered. Solution: Als
On 1 September 2016, Bram Moolenaar wrote:
>
> Patch 7.4.2299
> Problem:QuickFixCmdPre and QuickFixCmdPost autocommands are not always
> triggered.
> Solution: Also trigger on ":expr", ":cbuffer", etc. (Yegappan Lakshmanan)
> Files: src/quickfix.c, src/testdir/test_quickfix
On 2 September 2016, Justin M. Keyes wrote:
> On Thu, Sep 1, 2016 at 4:20 PM, LCD 47 wrote:
> > On 1 September 2016, Nikolay Aleksandrovich Pavlov
> > wrote:
> >> 2016-09-01 15:47 GMT+03:00 LCD 47 :
> >> > What is the recommended way to get the buffer n
On 1 September 2016, Nikolay Aleksandrovich Pavlov
wrote:
> 2016-09-01 15:47 GMT+03:00 LCD 47 :
> > What is the recommended way to get the buffer number of a file
> > starting from the filename?
> >
[...]
> > Based on the above (and taking a peek at the source
What is the recommended way to get the buffer number of a file
starting from the filename?
This is what the help has to say about bufnr():
: bufnr({expr} [, {create}])
: The result is the number of a buffer, as it is displayed by
: the ":ls" command. For the u
On 18 August 2016, Luc Hermitte wrote:
> > On 18 August 2016, Luc Hermitte wrote:
> > > Another point on the qflist topic is bugging me. IIRC, when an
> > > error is detected, the type flag is set to 'E'. But how is error
> > > detection done? Is it when the message 'error:' is detected? What
>
On 18 August 2016, Luc Hermitte wrote:
> Another point on the qflist topic is bugging me. IIRC, when an error
> is detected, the type flag is set to 'E'. But how is error detection
> done? Is it when the message 'error:' is detected? What about when the
> locale is in another language like 'fr_FR'
On 17 August 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Wed, Aug 17, 2016 at 1:48 AM, LCD 47 wrote:
> > On 16 August 2016, Yegappan Lakshmanan wrote:
> >> I am in particular interested in any comments/suggestions about the
> >> following new functions:
[...]
On 16 August 2016, Yegappan Lakshmanan wrote:
> I am in particular interested in any comments/suggestions about the following
> new functions:
>
> getbufinfo()
From the manual:
: Each returned List item is a dictionary with the following
: entries:
:
On 8 August 2016, Kent Sibilev wrote:
> On Monday, August 8, 2016 at 4:03:22 AM UTC-4, LCD 47 wrote:
>
> >
> > Wait, isn't the title already supposed to tell you that?
> >
>
> What do you mean by title?
From the manual (":h :copen"):
On 7 August 2016, Kent Sibilev wrote:
> On Saturday, August 6, 2016 at 1:02:18 PM UTC-4, Bram Moolenaar wrote:
> >
> > The problem with this solution is that the names are translated. A
> > more direct solution would be better.
> >
> > The 'buftype' option is "quickfix" for both quickfix and loca
On 27 July 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Tue, Jul 26, 2016 at 10:15 PM, LCD 47 wrote:
> > On 26 July 2016, Bram Moolenaar wrote:
> >>
> >> Lcd wrote:
> >>
> >> > On 25 July 2016, Yegappan Lakshmanan wrote:
> >> >
On 26 July 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 25 July 2016, Yegappan Lakshmanan wrote:
> > > Hi,
> > >
> > > On Mon, Jul 25, 2016 at 12:27 AM, LCD 47 wrote:
> > > > On 24 July 2016, Yegappan Lakshmanan
> > > &g
On 25 July 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Mon, Jul 25, 2016 at 12:27 AM, LCD 47 wrote:
> > On 24 July 2016, Yegappan Lakshmanan wrote:
> >> I am attaching a patch to enhance the getqflist/getloclist()
> >> functions to return the title string an
On 24 July 2016, Yegappan Lakshmanan wrote:
> I am attaching a patch to enhance the getqflist/getloclist() functions
> to return the title string and the setqflist()/setloclist() functions
> to set the title string.
>
> After this patch is incorporated, it will be easy to add the
> additional item
On 17 July 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Sun, Jul 17, 2016 at 10:00 PM, LCD 47 wrote:
> > On 17 July 2016, Yegappan Lakshmanan wrote:
> >> Hi,
> >>
> >> On Mon, Apr 13, 2015 at 5:04 AM, wrote:
> >> > Hello,
> >&
On 17 July 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Mon, Apr 13, 2015 at 5:04 AM, wrote:
> > Hello,
> >
> > I did not expect that many reactions. This is nice. Thank you all
> > for your interest in the matter.
> >
> >> > Ah, but as long as you are OK with that information showing up
> >> >
Is there any particular reason for not including colons ":" in
&iskeyword for VimL?
The current default makes it impossible to jump to definitions of
file-scoped functions and variables. Common ctags implementations
produce tags like this:
s:diff_ms autoload/peekaboo.vim /^functi
On 13 July 2016, Yang Luo wrote:
>
> I write a function like this:
> function InsertNumber(start, end, step)
>
> let i = a:start
>
> let curr_line = 0
>
> while i <= a:end
> if a:step <= 0
> echo "Error: step cannot <=0."
> break
> endif
>
> call append
On 10 July 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
[...]
> > Currently an error item from loclist looks like this:
> >
> > {
> > 'lnum': 148,
> > 'bufnr': 1,
> > 'col': 7,
> > 'valid': 1,
> > 'vcol': 0,
> >
On 9 July 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > > > > > On 7 July 2016, Bram Moolenaar wrote:
> > [...]
> > > > > I don't understand. What does "access to a buffer" mean?
> > > >
> > > > Syntastic is a sort of generalised compiler set, it runs
> > > > external compilers, and shows
On 9 July 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > > > On 7 July 2016, Bram Moolenaar wrote:
[...]
> > > I don't understand. What does "access to a buffer" mean?
> >
> > Syntastic is a sort of generalised compiler set, it runs
> > external compilers, and shows the results in a loclis
On 9 July 2016, Dominique Pellé wrote:
> LCD 47 wrote:
>
> > On 9 July 2016, Christian Brabandt wrote:
> >> On Fr, 08 Jul 2016, LCD 47 wrote:
> >>
> >> > Not recent, but do you remember the problem introduced by
> >> > 1640? It's
On 9 July 2016, Christian Brabandt wrote:
> On Fr, 08 Jul 2016, LCD 47 wrote:
>
> > Not recent, but do you remember the problem introduced by 1640?
> > It's still with us. _shrug_
>
> I don't follow. That was a bugfix for a crash and I believe it fixed
>
On 8 July 2016, LCD 47 wrote:
> On 8 July 2016, Bram Moolenaar wrote:
> >
> > Lcd wrote:
> >
> > > On 7 July 2016, Bram Moolenaar wrote:
> > > >
> > > > Patch 7.4.1997
> > > > Problem:Cannot ea
On 8 July 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Thu, Jul 7, 2016 at 7:31 AM, Yegappan Lakshmanan
> wrote:
> > Hi,
> >
> > On Thu, Jul 7, 2016 at 1:09 AM, LCD 47 wrote:
> >> On 6 July 2016, Yegappan Lakshmanan wrote:
> >>> Hi,
> &
On 8 July 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 7 July 2016, Bram Moolenaar wrote:
> > >
> > > Christian Brabandt wrote:
> > >
> > > > On Do, 07 Jul 2016, Bram Moolenaar wrote:
> > > >
> > > > >
> > > > > There has been a request that when adding items to the
> > > > > quickfix list
On 8 July 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 7 July 2016, Bram Moolenaar wrote:
> > >
> > > Patch 7.4.1997
> > > Problem:Cannot easily scroll the quickfix window.
> > > Solution: Add ":cbottom".
> > [...]
> >
> > This doesn't seem to work with loclist windows. For
On 7 July 2016, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Do, 07 Jul 2016, Bram Moolenaar wrote:
> >
> > >
> > > There has been a request that when adding items to the quickfix
> > > list, no buffer is created to hold the file name.
> > >
> > > The reason is that when there are
On 7 July 2016, Bram Moolenaar wrote:
>
> Patch 7.4.1997
> Problem:Cannot easily scroll the quickfix window.
> Solution: Add ":cbottom".
[...]
This doesn't seem to work with loclist windows. For what it's
worth.
/lcd
--
--
You received this message from the "vim_dev" maillist.
On 6 July 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Wed, Jul 6, 2016 at 2:18 PM, Daniel Hahler
> wrote:
> >
> > set buftype=nofile
> > set noequalalways
> > call setqflist([{'lnum': 1, 'bufnr': 1, 'col': 0, 'valid': 1, 'vcol': 0,
> 'nr': 0, 'type': 'E', 'pattern': '', 'text': 'msg'}])
> > co
Parse::RecDescent(3) is a valid man page on UNIX (comming from the
Perl module Parse::RecDescent), and it's case-sensitive. Running it
through Vim's MANPAGER produces the following errors:
Error detected while processing function 136_MANPAGER:
line 16:
E684: list ind
On 10 June 2016, Ramel Eshed wrote:
> Hi,
>
> There were few updates to this file in
> https://github.com/vim-perl/vim-perl/blob/master/ftplugin/perl.vim
> since Jul 2013. The version distributed with Vim sets the global
> value of iskeyword. It already fixed in Oct 2013.
+1, there are many
On 4 June 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > > > Scenario:
> > > >
> > > > (1) umask 0177
> > > > (2) run Vim
> > > > (3) in Vim run system(), say:
> > > >
> > > > :echo system('ls')
> > > >
> > > > On Linux machines the result is:
> > > >
> > > > E484:
On 4 June 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > Scenario:
> >
> > (1) umask 0177
> > (2) run Vim
> > (3) in Vim run system(), say:
> >
> > :echo system('ls')
> >
> > On Linux machines the result is:
> >
> > E484: Can't open file /tmp/viEkD0f/2
> >
> >
Scenario:
(1) umask 0177
(2) run Vim
(3) in Vim run system(), say:
:echo system('ls')
On Linux machines the result is:
E484: Can't open file /tmp/viEkD0f/2
It's easy to see why:
$ ls -ld /tmp/viEkD0f
drw--- 2 1034 1023 40 Jun 4 13:32 /tmp/viEkD
On 2 May 2016, Damien wrote:
> Le Sun, May 01, 2016 at 09:23:04PM +0300, LCD 47 a écrit :
> > This seems to be a recent change in Perl rather than Vim:
> >
> > clang -c -I. -Iproto -DHAVE_CONFIG_H -pipe -O2 -U_FORTIFY_SOURCE
> > -D_FORTIFY_SOURCE=1
This seems to be a recent change in Perl rather than Vim:
clang -c -I. -Iproto -DHAVE_CONFIG_H -pipe -O2 -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1 -I/usr/include/python3.5m -DPYTHON3_HOME='L"/usr"'
-pthread -DDYNAMIC_PYTHON3_DLL=\"libpython3.5m.so.1.0\" -o
objects/if_python3.o if_pyt
On 26 April 2016, Bram Moolenaar wrote:
>
> James McCoy wrote:
>
> > On Mon, Apr 25, 2016 at 11:06:43PM +0200, Bram Moolenaar wrote:
> > >
> > > Andrew Stewart wrote:
> > >
> > > > This handler gets called just about immediately, as expected, but
> > > > a:message is always 'DETACH', not the d
On 12 April 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Tue, Apr 12, 2016 at 9:59 AM, LCD 47 wrote:
[...]
> > Currently .ll when jumping to file "example.txt" line N goes
> > roughly like this:
> >
> > (1) load "example.txt"
> >
On 12 April 2016, Yegappan Lakshmanan wrote:
> LCD 47 wrote:
[...]
> > Can you please give an example when setting the cursor before an
> > autocmd would "break functionality that depends on these events"?
> >
>
> Consider for example, you have
On 12 April 2016, Dominique Pellé wrote:
> LCD 47 wrote:
>
> > On 12 April 2016, Dominique Pellé wrote:
> >> LCD 47 wrote:
> >>
> >> > Sorry, but no. The autocmd can mess things up beyond repair without
> >> > touching touching the
On 12 April 2016, Christian Brabandt wrote:
> Am 2016-04-12 08:40, schrieb LCD 47:
> > On 11 April 2016, Yegappan Lakshmanan wrote:
> >> Hi,
> >>
> >> On Mon, Apr 11, 2016 at 11:37 AM, LCD 47 wrote:
> >> > On 11 April 2016, Christian Brabandt wr
On 12 April 2016, Dominique Pellé wrote:
> LCD 47 wrote:
>
> > Sorry, but no. The autocmd can mess things up beyond repair without
> > touching touching the loclist. Example:
> >
> > (1) start jumping to line 500 in exmple.txt
> > (2) example.txt has a B
On 11 April 2016, Yegappan Lakshmanan wrote:
> Hi,
>
> On Mon, Apr 11, 2016 at 11:37 AM, LCD 47 wrote:
> > On 11 April 2016, Christian Brabandt wrote:
> >> Am 2016-04-11 08:20, schrieb LCD 47:
> >> > On 19 March 2016, Dominique Pellé wrote:
> >>
On 11 April 2016, Christian Brabandt wrote:
> Am 2016-04-11 08:20, schrieb LCD 47:
> > On 19 March 2016, Dominique Pellé wrote:
> >> Hi LCD,
> >>
> >> If you can still reproduce this bug, can you check
> >> whether recent patch 7.4.1592 fix
x27;s feet, but the fact that an autocmd can happen in the middle
of the operation is still a bug, I think.
/lcd
On 19 March 2016, Dominique Pellé wrote:
> LCD 47 wrote:
>
> > On 23 July 2014, Bram Moolenaar wrote:
> >>
> >> Lcd wrote:
> >&
On 5 April 2016, Nikolay Aleksandrovich Pavlov wrote:
> 2016-04-05 13:52 GMT+03:00 LCD 47 :
> > On 4 April 2016, Bram Moolenaar wrote:
[...]
> >> Lcd wrote:
> > [...]
> >> > There is still the issue of finding scripts depth-first. This is
> >
On 4 April 2016, Bram Moolenaar wrote:
>
> I have been wondering if the next release should be called 7.5 or 8.
> We have quite a few new features, but not that many as with the Vim 7
> release. Well, that was a big release. I think the most important
> addition since then is persistent undo in
On 4 April 2016, Bram Moolenaar wrote:
> tldr: Proposal: Change loading packages from pack/start (and
> :packloadall) to first add all directories to 'runtimepath' before
> sourcing the plugins.
After pondering about it for a while, I'm pretty sure this is the
right thing to do. It closes al
On 3 April 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > > > Error detected while processing
> > > > /home/lcd047/Git/Vim/textobj-comment/plugin/textobj/comment.vim:
> > > > line 27:
> > > > E117: Unknown function: textobj#user#plugin
> > > > Press ENTER or type command to continue
[...]
>
On 3 April 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > > > On 2 April 2016, Bram Moolenaar wrote:
> > > > >
> > > > > Patch 7.4.1699
> > > > > Problem::packadd does not work the same when used early or late.
> > > > > Solution: Always load plugins matching "plugin/**/*.vim".
> > > >
On 3 April 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 2 April 2016, Bram Moolenaar wrote:
> > >
> > > Patch 7.4.1699
> > > Problem::packadd does not work the same when used early or late.
> > > Solution: Always load plugins matching "plugin/**/*.vim".
> > > Files: src/ex_cm
On 2 April 2016, Bram Moolenaar wrote:
>
> Patch 7.4.1699
> Problem::packadd does not work the same when used early or late.
> Solution: Always load plugins matching "plugin/**/*.vim".
> Files: src/ex_cmds2.c, src/testdir/test_packadd.vim
>
>
> *** ../vim-7.4.1698/src/ex_cmds2.c2
On 27 March 2016, Bram Moolenaar wrote:
>
> Tyru wrote:
>
[...]
> > * In some places in repeat.txt, backtick(`) was used instead of bar(|)
> > like `:packadd`.
> > But almost quoted words seem to have its own helptag.
> > If there is a helptag, it should be quoted by bar so a user can jump i
On 19 March 2016, Dominique Pellé wrote:
> LCD 47 wrote:
[...]
> >
> > As I said, I can't reproduce the problem in a simpler setup. As
> > any self-respecting Heisenbug, I can't even reproduce it in gdb.
> >
> > /lcd
> >
>
> Hi
On 14 March 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
> > On 12 March 2016, Bram Moolenaar wrote:
> > >
> > > Patch 7.4.1551
> > > Problem:Cannot generate help tags in all doc directories.
> > > Solution: Make ":helptags ALL" work.
> > > Files: src/ex_cmds2.c, src/proto/ex_cmds2.
On 12 March 2016, Bram Moolenaar wrote:
>
> Patch 7.4.1551
> Problem:Cannot generate help tags in all doc directories.
> Solution: Make ":helptags ALL" work.
> Files: src/ex_cmds2.c, src/proto/ex_cmds2.pro, src/ex_cmds.c, src/vim.h,
> src/testdir/test_packadd.vim
[...]
On 13 March 2016, Bram Moolenaar wrote:
>
> I wrote:
>
> > Patch 7.4.1553
> > Problem:":runtime" does not use 'packpath'.
> > Solution: Add "what" argument.
> > Files: src/ex_cmds2.c, src/vim.h, runtime/doc/repeat.txt,
> > src/testdir/test_packadd.vim
>
> This completes t
On 8 March 2016, Bram Moolenaar wrote:
>
> Patch 7.4.1516
> Problem:Cannot change file permissions.
> Solution: Add setfperm().
[...]
> + setfperm({fname}, {mode}) *setfperm()* *chmod*
> + Set the file permissions for {fname} to {mode}.
> +
On 7 March 2016, Bram Moolenaar wrote:
>
> Lcd wrote:
>
[...]
> > The point is, the main problem packages are supposed to solve
> > is to be able to distribute groups of plugins as packages. So one
> > could have:
> >
> > pack/mypack1/opt/plugin1
> > pack/mypack1/opt/library
On 7 March 2016, Ben Fritz wrote:
> On Monday, March 7, 2016 at 3:18:06 PM UTC-6, Bram Moolenaar wrote:
> > Lcd wrote:
> >
> > > Placing a colour scheme like this should work, but it doesn't:
> > >
> > > $VIM/vimfiles/pack/my/ever/molokai/colors/molokai.vim
> > >
> > > The reason i
With an optional package placed like this:
pack/my/opt/mydebug/plugin/debugger.vim
one can enable it with a packadd:
packadd mydebug
However, it seems to me it would make more sense to be able to do it
by calling:
packadd my
The point is, the main problem p
Placing a colour scheme like this should work, but it doesn't:
$VIM/vimfiles/pack/my/ever/molokai/colors/molokai.vim
The reason it doesn't work is that mandatory plugins are sourced
after vimrc, and thus the new scheme can't be set from vimrc.
To make it work, it can be made
1 - 100 din 320 matches
Mail list logo
