Hallo Joachim!
Joachim Breitner schrieb am Montag, den 23. März 2015:
> Hi,
>
> On Fri, 23 Jan 2015 10:30:59 +0100 Christian Brabandt wrote:
> > Note, this bug has been fixed upstream with 7.4.576
> > (the commit message mentions relativenumber setting, but the patch
> > actually has nothing t
Hi,
On Fri, 23 Jan 2015 10:30:59 +0100 Christian Brabandt wrote:
> Note, this bug has been fixed upstream with 7.4.576
> (the commit message mentions relativenumber setting, but the patch
> actually has nothing to do with it.)
great!
I keep rebuilding vim with every upload to add this patch. A
Note, this bug has been fixed upstream with 7.4.576
(the commit message mentions relativenumber setting, but the patch
actually has nothing to do with it.)
Best,
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact l
Package: vim
Version: 2:7.4.488-4
Followup-For: Bug #774492
Control: tag -1 + patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
there seems to be the same or a related bug mentioned at
https://www.mail-archive.com/vim_dev@googlegroups.com/msg30754.html
Attached is a file to reproduce this
Package: vim
Version: 2:7.4.488-3
Severity: normal
When the 'linebreak' option (visually break long lines at spaces only
rather than at a middle of a word) is set "c{motion}" command (but not
"d" or "x" or "i") cause current real line to be re-flowed like as the
'linebreak' is not set.
This
5 matches
Mail list logo
