Patch 8.1.2056
Problem:"make test" for indent files doesn't cause make to fail.
Solution: Exit the script with ":cquit". (Daniel Hahler, closes #4949)
Files: runtime/indent/testdir/runtest.vim, .gitignore
*** ../vim-8.1.2055/runtime/indent/testdir/runtest.vim 2018-12-15
17:43:38.87
Paul Jolly wrote:
> > OK, so the feedkeys() causes the safe state to be reset. That is
> > correct, since Vim is then busy with processing input, which isn't
> > considered safe.
> >
> > The problem is that with the "xt" argument to feedkeys() the input is
> > processed right away, and we don't
Patch 8.1.2055
Problem:Not easy to jump to function line from profile.
Solution: Use "file:99" instead of "file line 99" so that "gf" works.
(Daniel Hahler, closes #4951)
Files: src/profiler.c, src/testdir/test_profile.vim
*** ../vim-8.1.2054/src/profiler.c 2019-08-3
Patch 8.1.2054
Problem:Compiler test for Perl may fail.
Solution: Accept any error line number. (James McCoy, closes #4944)
Files: src/testdir/test_compiler.vim
*** ../vim-8.1.2053/src/testdir/test_compiler.vim 2019-07-31
22:18:19.335852519 +0200
--- src/testdir/test_compiler.
Patch 8.1.2053
Problem:SafeStateAgain not triggered if callback uses feedkeys().
Solution: Check for safe state in the input loop. Make log messages easier
to find. Add 'S' flag to state().
Files: src/main.c, src/proto/main.pro, src/getchar.c,
runtime/doc/eval.
Am 18.09.2019 um 00:09 schrieb CrispyDrone (Vim Github Repository):
*Describe the bug*
I've exhausted all options and followed the documentation but am unable to get
|:! {cmd}| to work with the following shell configuration:
|set shell=\"$PROGRAMW6432\Git\bin\bash.exe\"
|
I've also the tried t
On Mi, 18 Sep 2019, 'Andy Wokula' via vim_dev wrote:
> So it's ok when `dl' deletes that fold?
No I don't think so. Do you think so because x is expected to work like
'dl' and `l` is expected to move to the next line?
> And `x' is documented to behave like `dl'. So it's ok to add a special ca
Am 18.09.2019 um 17:42 schrieb Christian Brabandt:
On Mi, 18 Sep 2019, 'Andy Wokula' via vim_dev wrote:
Am 17.09.2019 um 22:45 schrieb Bram Moolenaar:
Patch 8.1.2052
Problem:Using "x" before a closed fold may delete that fold.
Solution: Do not translate 'x' do "dl". (Christian Brabandt,
Hi,
On Wed, Sep 18, 2019 at 8:47 AM 'Andy Wokula' via vim_dev
wrote:
>
> Am 18.09.2019 um 17:18 schrieb Yegappan Lakshmanan:
> > Hi all,
> >
> > Currently the following Vim built-in functions are available to get
> > information about individual marks: getpos(), line() and col().
> >
> > But we d
Am 18.09.2019 um 17:18 schrieb Yegappan Lakshmanan:
Hi all,
Currently the following Vim built-in functions are available to get
information about individual marks: getpos(), line() and col().
But we don't have a function to get the list of marks placed in a
buffer or the list of global marks (s
On Mi, 18 Sep 2019, 'Andy Wokula' via vim_dev wrote:
> Am 17.09.2019 um 22:45 schrieb Bram Moolenaar:
> > Patch 8.1.2052
> > Problem:Using "x" before a closed fold may delete that fold.
> > Solution: Do not translate 'x' do "dl". (Christian Brabandt, closes #4927)
> > Files: src/n
Am 17.09.2019 um 22:45 schrieb Bram Moolenaar:
Patch 8.1.2052
Problem:Using "x" before a closed fold may delete that fold.
Solution: Do not translate 'x' do "dl". (Christian Brabandt, closes #4927)
Files: src/normal.c, src/testdir/test_fold.vim
So it's ok when `dl' deletes that fold?
Hi all,
Currently the following Vim built-in functions are available to get
information about individual marks: getpos(), line() and col().
But we don't have a function to get the list of marks placed in a
buffer or the list of global marks (similar to the list displayed by
the :marks command).
> OK, so the feedkeys() causes the safe state to be reset. That is
> correct, since Vim is then busy with processing input, which isn't
> considered safe.
>
> The problem is that with the "xt" argument to feedkeys() the input is
> processed right away, and we don't return to the main loop. I gues
Paul Jolly wrote:
> > OK, so the whole sequence is triggered by the balloon eval
> > functionality. This happens in check_due_timer(). That's a fairly
> > normal way a callback is invoked, in this case evaluating 'balloonexpr'.
>
> Ok, thanks.
>
> > You can see in line 409:
> > 0.181045 :
On Mi, 18 Sep 2019, Tony Mechelynck wrote:
> When the cursor is on an end-of-line (even without 'list', which I
> use) I would expect that x, or dl, would join the current line with
> the next one. Not that it'd be a no-op.
So `dd` would be wrong?
Best,
Christian
--
Alle wollen zurück zur Nat
On Wed, Sep 18, 2019 at 1:46 PM Christian Brabandt wrote:
>
>
> On Mi, 18 Sep 2019, Bram Moolenaar wrote:
>
> > Let's be practical: We fixed something because a user complained and it
> > was clear it had to be fixed. For "x" deleting a line we did not get
> > complaints. And, depending on how y
On Mi, 18 Sep 2019, Christian Brabandt wrote:
> On Mi, 18 Sep 2019, Bram Moolenaar wrote:
>
> > Let's be practical: We fixed something because a user complained and it
> > was clear it had to be fixed. For "x" deleting a line we did not get
> > complaints. And, depending on how you look at it,
> OK, so the whole sequence is triggered by the balloon eval
> functionality. This happens in check_due_timer(). That's a fairly
> normal way a callback is invoked, in this case evaluating 'balloonexpr'.
Ok, thanks.
> You can see in line 409:
> 0.181045 : safe state reset
>
> That's why it st
On Mi, 18 Sep 2019, Bram Moolenaar wrote:
> Let's be practical: We fixed something because a user complained and it
> was clear it had to be fixed. For "x" deleting a line we did not get
> complaints. And, depending on how you look at it, if "l" crosses line
> boundaries, it makes sense that "
> > How does the mouse move trigger the sequence?
>
> Sorry, I should have covered that before. This is a hover test, so I
> use test_setmouse followed by:
>
> feedkeys("\\", "xt")
>
> It's then the balloonexpr function that triggers the ch_evalexpr in
> point 1 above.
OK, so the whole se
Christian wrote:
> On Di, 17 Sep 2019, Bram Moolenaar wrote:
>
> > Patch 8.1.2052
> > Problem:Using "x" before a closed fold may delete that fold.
> > Solution: Do not translate 'x' do "dl". (Christian Brabandt, closes #4927)
> > Files: src/normal.c, src/testdir/test_fold.vim
>
> How does the mouse move trigger the sequence?
Sorry, I should have covered that before. This is a hover test, so I
use test_setmouse followed by:
feedkeys("\\", "xt")
It's then the balloonexpr function that triggers the ch_evalexpr in
point 1 above.
I've attached the channel log file - th
23 matches
Mail list logo
