It would be helpful to be able to highlight the indicator for continuation
lines (showbreak) differently from that of the EOT markers (~, @). While the
first indicator usually profits from a good visibility, the latter preferably
uses some dim colors. At the moment there exists only one
Trying to :read a remote file on VimEnter results in
Error detected while processing VimEnter Auto commands for *:
E484: Can't open file http://www.openssh.org/txt/rfc1349.txt
I used the following minimal vimrc with Vim 7.4a.
filetype plugin indent on
autocmd VimEnter * read
On Sun, Jul 7, 2013 at 11:44 AM, glts 676c7...@gmail.com wrote:
Trying to :read a remote file on VimEnter results in
Error detected while processing VimEnter Auto commands for *:
E484: Can't open file http://www.openssh.org/txt/rfc1349.txt
I used the following minimal vimrc with Vim
On 07/07/13 12:07, glts wrote:
On Sun, Jul 7, 2013 at 11:44 AM, glts 676c7...@gmail.com wrote:
Trying to :read a remote file on VimEnter results in
Error detected while processing VimEnter Auto commands for *:
E484: Can't open file http://www.openssh.org/txt/rfc1349.txt
I used the
On 07/07/13 13:02, Tony Mechelynck wrote:
On 07/07/13 12:07, glts wrote:
On Sun, Jul 7, 2013 at 11:44 AM, glts 676c7...@gmail.com wrote:
Trying to :read a remote file on VimEnter results in
Error detected while processing VimEnter Auto commands for *:
E484: Can't open file
Simon Ruderich wrote:
Hello,
Running the testsuite for the latest Vim (7.4a.1) shows these
errors when running test89:
==10670== Invalid write of size 1
==10670==at 0x4C29552: strcpy (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10670==by 0x214DEA:
David Burgin wrote:
Trying to :read a remote file on VimEnter results in
Error detected while processing VimEnter Auto commands for *:
E484: Can't open file http://www.openssh.org/txt/rfc1349.txt
I used the following minimal vimrc with Vim 7.4a.
filetype plugin indent on
ZyX wrote:
Just mentioned: help file (:h diffoff) still says that options are
restore to their default values.
Right, I forgot to update that.
--
The Law, in its majestic equality, forbids the rich, as well as the
poor, to sleep under the bridges, to beg in the streets, and to steal
bread.
Simon Ruderich wrote:
Resending this patch.
It conceals the and markers in the help syntax. Useful
for terminal emulators with pseudo transparency like urxvt. It
supports Vim without the conceal feature.
Hmm, I suppose that should work. Let's include it and check it doesn't
cause
Simon Ruderich wrote:
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 72eaeef..21cc352 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -4646,7 +4646,7 @@ A jump table for the options with a short description=
can be found at |Q_op|.
The
On Sun, Jul 7, 2013 at 1:07 PM, Bram Moolenaar b...@moolenaar.net wrote:
David Burgin wrote:
Trying to :read a remote file on VimEnter results in
Error detected while processing VimEnter Auto commands for *:
E484: Can't open file http://www.openssh.org/txt/rfc1349.txt
I used the
On Sun, Jul 7, 2013 at 1:05 PM, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 07/07/13 13:02, Tony Mechelynck wrote:
On 07/07/13 12:07, glts wrote:
On Sun, Jul 7, 2013 at 11:44 AM, glts 676c7...@gmail.com wrote:
Trying to :read a remote file on VimEnter results in
Error
Dominique Pelle wrote:
Bram Moolenaar b...@moolenaar.net wrote:
Simon Ruderich wrote:
Hello,
Running the testsuite for the latest Vim (7.4a.1) shows these
errors when running test89:
==10670== Invalid write of size 1
==10670==at 0x4C29552: strcpy (in
Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 06:53 Zeit:
You should already have it.
Oh, right, thanks!
But why does it still make 7.3? :-/ (I use MS Windows, VS 2010.)
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are
Patch 7.4a.002
Problem:Valgrind errors in test 89. (Simon Ruderich)
Solution: Allocate one more byte. (Dominique Pelle)
Files: src/misc2.c
*** ../vim-7.4a.001/src/misc2.c 2013-07-04 21:14:48.0 +0200
--- src/misc2.c 2013-07-07 16:03:35.0 +0200
***
***
On 07/07/13 15:26, tux- wrote:
Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 06:53 Zeit:
You should already have it.
Oh, right, thanks!
But why does it still make 7.3? :-/ (I use MS Windows, VS 2010.)
Oh, does it? Mine (on Linux) doesn't. Try doing a full make (i.e.,
telling Make to
Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:22 Zeit:
Are you sure your current changeset (hg log -r . without the quotes)
is on the default branch and is a descendant of v7-4a-001?
hg tags says 7.4 is current. :-/
The hg up command did not change anything, version.h also says 7.4.
On 07/07/13 16:16, Bram Moolenaar wrote:
Patch 7.4a.002
Problem:Valgrind errors in test 89. (Simon Ruderich)
Solution: Allocate one more byte. (Dominique Pelle)
Files: src/misc2.c
Notwithstanding the email's Subject, this is indeed patch 7.4a.002.
Best regards,
Tony.
--
The
On 07/07/13 16:39, tux- wrote:
Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:22 Zeit:
Are you sure your current changeset (hg log -r . without the quotes)
is on the default branch and is a descendant of v7-4a-001?
hg tags says 7.4 is current. :-/
The hg up command did not change
Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:47 Zeit:
Did you install, or at leat run, your new Vim, to see its version?
Yup, it's 7.3.some patch.
I think it's C:\Program Files\Vim\vim74a or something, NOT
...\vim73 as it used to be.
Yep, it is, I manually renamed the folder.
But
Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.4a BETA
This is the first BETA release of Vim 7.4.
Please check that the distribution is OK. I haven't done one for a long
time. Report anything that isn't right. That includes a crash but also
a typo in the documentation
21 matches
Mail list logo
