-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On September 29, 2014 10:39:16 PM GMT+03:00, Marco Hinz
wrote:
>> Well, I suppose there is something to say for both ways. What do the
>> users prefer?
>
>I understand that such visual changes are almost always controversial,
>especially for such a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On September 26, 2014 6:10:35 AM GMT+03:00, Tony Mechelynck
wrote:
>On 25/09/14 10:24, mattn wrote:
>>> I don't see what you mean with "breakable".
>>
>> Sorry, I was confused. Until Patch 7.4.457, getchar() doesn't return
>"\". (However 0x80 0xFD
$ ls | vim -
About reading stdin, it' is PIPE. And vim handles fileencodings conversion. But
$ vim -u NONE --cmd "e ++enc=utf-8" --cmd "set fileencodings=cp932,utf-8"
<(echo "foobar")
It is not PIPE. it's FIFO. So vim doesn't handle fileencodings. I'm thinking
it's possible to handle fileencod
Sorry, but I mean, when using , we need to handle \.
Is this right behavior?
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this messa
small followup. Just noticed that moving cursor around wrapped line is totally
buggy now. I Didn't see that earlier since I keep wrapping off all the time,
just turned it on now to check... So... this all needs a bit more effort I
suppose :)
Mikhail
--
--
You received this message from the
Guten Tag Christian,
I have managed to compile with this patch under windows with msvs Express 2008.
New feature works exactly how I expected. Thank you very much for the effort.
I must say however after playing with it for a while I discovered some
artefacts are appearing along the text border
On 9/29/14, 12:09 PM, Bram Moolenaar wrote:
Marco Hinz wrote:
win_draw_end() is used to clear the end of the screen in certain
cases, e.g. very long, wrapped lines or the actual end of the buffer.
Fold and sign columns get continued although that's not useful at
all for the case of the end of
Hi,
I noticed some problems with Vim displaying lines, that are longer than
the actual screen size.
For one, if the precedes listchar option is set, this will be drawn even
when 'showbreak' is set and the list option is not. The easy fix is:
diff --git a/src/screen.c b/src/screen.c
--- a/src/sc
On Mon, Sep 29, 2014 at 2:39 PM, Marco Hinz wrote:
> > Well, I suppose there is something to say for both ways. What do the
> > users prefer?
>
> I understand that such visual changes are almost always controversial,
> especially for such a long-lasting editor with its big community.
>
> I'd argu
Yasuhiro Matsumoto wrote:
> After starting cmd.exe on japanese windows, the title string is
> 「コマンドプロンプト」. Vim break it while executing commands. And I
> noticed that vim restoreing broken title string.
>
> g_szOrigTitle is ANSI encoding. But vim call mch_settitle which is
> depend on current en
Christian wrote:
> On Mi, 24 Sep 2014, Gevisz wrote:
> > Some abbreviations expand as desired and some do not.
> >
> > > Are there any circumstances different between a working abbreviation
> > > and a not working abbreviation?
> >
> > They may be very similar. For example, abbreviation чкпк ex
Yasuhiro Matsumoto wrote:
> When printer name contains multi-byte, the name is displayed as ???.
Thanks!
--
hundred-and-one symptoms of being an internet addict:
200. You really believe in the concept of a "paperless" office.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.
Shahbaz Youssefi wrote:
> On Monday, May 26, 2014 8:18:38 PM UTC+2, Bram Moolenaar wrote:
> > Marek Zaffy wrote:
> >
> > Looks like the newer Posix signals are missing. My man page says they
> >
> > are for Posix 2001. Let's add this then:
> >
> > " POSIX 2001
> >
> > syn keyword cConst
> Well, I suppose there is something to say for both ways. What do the
> users prefer?
I understand that such visual changes are almost always controversial,
especially for such a long-lasting editor with its big community.
I'd argue that this patch makes the fold and sign column work as the
numb
Patch 7.4.463
Problem:Test 86 and 87 may hang on MS-Windows.
Solution: Call inputrestore() after inputsave(). (Ken Takata)
Files: src/testdir/test86.in, src/testdir/test87.in
*** ../vim-7.4.462/src/testdir/test86.in2014-03-12 15:26:36.428714415
+0100
--- src/testdir/test86.in
On 29 September 2014, toothpik wrote:
> On Mon, Sep 29, 2014 at 06:09:23PM +0200, Bram Moolenaar wrote:
>
> > Marco Hinz wrote:
>
> > > win_draw_end() is used to clear the end of the screen in certain
> > > cases, e.g. very long, wrapped lines or the actual end of the buffer.
> > >
> > > Fold a
Updates:
Status: Fixed
Comment #4 on issue 3 by chrisbr...@googlemail.com: Combining
completeopt=menu,preview and cursorcolumn will make completion menu vanish
https://code.google.com/p/vim/issues/detail?id=3
Fixed by 7.3.807
--
You received this message because this project is confi
Updates:
Status: Fixed
Comment #3 on issue 48 by chrisbr...@googlemail.com: E490 foldopen error
can't be caught
https://code.google.com/p/vim/issues/detail?id=48
Fixed by 7.3.637
--
You received this message because this project is configured to send all
issue notifications to this
On Mon, Sep 29, 2014 at 06:09:23PM +0200, Bram Moolenaar wrote:
> Marco Hinz wrote:
> > win_draw_end() is used to clear the end of the screen in certain
> > cases, e.g. very long, wrapped lines or the actual end of the buffer.
> >
> > Fold and sign columns get continued although that's not usefu
Ken Takata wrote:
> After 7.4.084, test86 and 87 stop in the input mode on Windows.
> It is caused by inputsave() and feedkeys(), I think.
> The following patch seems to fix this:
Thanks!
--
hundred-and-one symptoms of being an internet addict:
197. Your desk collapses under the weight of your
Marco Hinz wrote:
> win_draw_end() is used to clear the end of the screen in certain
> cases, e.g. very long, wrapped lines or the actual end of the buffer.
>
> Fold and sign columns get continued although that's not useful at
> all for the case of the end of buffer.
>
> Therefore win_draw_end(
Hirohito Higashi wrote:
> Hi Peter and Bram,
>
> 2014/9/27(Sat) 5:00:01 UTC+9 Peter Mattern:
> > As of 7.4.459 the script files as created by mksession or mkview contain
> >
> > an invalid line
> >
> >setlocal backupcopy=
> >
> > which causes an E474 error when sourced.
> >
> >
Patch 7.4.462
Problem:Setting the local value of 'backupcopy' empty gives an error.
(Peter Mattern)
Solution: When using an empty value set the flags to zero. (Hirohito
Higashi)
Files: src/option.c
*** ../vim-7.4.461/src/option.c 2014-09-23 15:45:04.870801055 +
This option should contain one of "yes", "no" or "auto". However, global /
local string option should allow the empty option for local. It is not possible
after Vim7.4.456.
My patch fixed this.
Thank you.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your
Hi Peter and Bram,
2014/9/27(Sat) 5:00:01 UTC+9 Peter Mattern:
> As of 7.4.459 the script files as created by mksession or mkview contain
>
> an invalid line
>
>setlocal backupcopy=
>
> which causes an E474 error when sourced.
>
>
>
> Once a correct value such as auto was set ma
25 matches
Mail list logo
