Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 320 by enno.na...@gmail.com: option to enable autogenerated
server-name under Terminal Vim in Linux
https://code.google.com/p/vim/issues/detail?id=320
What steps will reproduce the problem?
1. Enter a terminal in Linux, su
Hi,
On Jan 21, 2015, at 3:01, Bram Moolenaar wrote:
> Patch 7.4.587
> Problem:Conceal does not work properly with 'linebreak'. (cs86661)
> Solution: Save and restore boguscols. (Christian Brabandt)
> Files:src/screen.c, src/testdir/test_listlbr_utf8.in,
> src/testdir/
Comment #3 on issue 319 by dhah...@gmail.com: New option to not beep
with 'showmatch'
https://code.google.com/p/vim/issues/detail?id=319
The bell serves its purpose in general and disabling it altogether because
of
this seems to be overkill.
I have it disabled in my terminal (but mostly b
On Saturday, January 17, 2015 at 1:20:04 PM UTC-6, Bram Moolenaar wrote:
>
> Since undo works by saving the line before changing it, restricting the
> "keep undo" modifier to only work when the cursor remains in the same
> line should work. It's also fairly easy to understand, instead of
> making
Comment #4 on issue 319 by chrisbr...@googlemail.com: New option to not
beep with 'showmatch'
https://code.google.com/p/vim/issues/detail?id=319
Anything wrong with this approach? Simply reset the bell setting when
Entering Insert mode and reset it when returning. I don't think, we want to
Hi Bram!
On Di, 20 Jan 2015, Bram Moolenaar wrote:
> Thinking about this again: It should be OK to store the column and the
> computed virtual column. These do not depend on the RE state. When
> trying several states at the same position the virtual column will be
> computed only once. And whe
Am Dienstag, 20. Januar 2015 22:53:48 UTC+1 schrieb Christian Brabandt:
> Hi Tim!
>
> On So, 18 Jan 2015, Tim Lebedkov wrote:
>
> > Am Sonntag, 18. Januar 2015 14:36:52 UTC+1 schrieb Bram Moolenaar:
> > > Tim Lebedkov wrote:
> > >
> > > > my patch "Switch the NSIS installer to MUI2"
> > > > (htt
Hi Tim!
On Mi, 21 Jan 2015, Tim Lebedkov wrote:
> I did, but everything I hear is that the changes will be merged maybe
> in 2016 (and maybe not).
I can understand, that this is frustrating and I have felt the same,
when I noticed, that some of my patches are still in the todo list (and
get th
On Wednesday, January 21, 2015 at 1:33:35 PM UTC-6, Tim Lebedkov wrote:
> > For a beginning, you could maintain a separate installer so that people
> > can actually try that it works and you get feedback. Then you can also
> > gradually change further things, if this is required.
>
> I did, but
Am Montag, 19. Januar 2015 16:30:46 UTC+1 schrieb Craig Skinner:
> Hi folks,
>
> This is my 1st post here:
>
> The diff below works to case de-sensitise mth/day in crontab files.
>
> crontab(5) man page saith:
> ...
> Names can be used in the month and day-of-week fields. Use the firs
Updates:
Status: New
Labels: runtime
Comment #4 on issue 132 by chrisbr...@googlemail.com: Crontab syntax
highlighting doesn't work properly when day/month names are not lowercased
https://code.google.com/p/vim/issues/detail?id=132
(still unsolved, reopening).
Patch also avai
Hello,
Since around last year I experience very frequent vim crashes. This is caused
by Lua written plugin neocomplete.vim. Plugin's author reply was: "Vim plugins
cannot crash Vim. It seems if_lua garbage collection bug."
The crash is very difficult to reproduce. It takes from 10min to several
Hi
The regexp .\{1,9000} is very slow with the new regexp engine
compared to the old engine. Compare the timing of those 2
commands where the only difference is set re=1 vs set re=2:
$ time vim -X -u NONE \
-c 'set re=1' \
-c 'call feedkeys("ihello\/.\\{1,9000}\:q!\")'
real0m0.004s
use
Dominique Pellé wrote:
> Hi
>
> The regexp .\{1,9000} is very slow with the new regexp engine
> compared to the old engine. Compare the timing of those 2
> commands where the only difference is set re=1 vs set re=2:
>
> $ time vim -X -u NONE \
>-c 'set re=1' \
>-c 'call feedkeys("ihello\/
On Wed, Jan 21, 2015 at 3:02 PM, Ben Fritz wrote:
> On Wednesday, January 21, 2015 at 1:33:35 PM UTC-6, Tim Lebedkov wrote:
> >
> > > > my patch "Switch the NSIS installer to MUI2"
> > > > (https://code.google.com/p/vim/issues/detail?id=279) was not
> > > > merged in 2 months. This is clearly too
On Wed, Jan 21, 2015 at 12:10:50PM -0800, Christian Brabandt wrote:
> This has also been requested in issue 132
> (https://code.google.com/p/vim/issues/detail?id=132).
> @Bram, the maintainer seems to be unreachable and this is a relative
> small change, so perhaps you'd like to include that chan
On Wed, Jan 21, 2015 at 02:32:29PM -0800, Sergey Vlasov wrote:
> Since around last year I experience very frequent vim crashes. This is
> caused by Lua written plugin neocomplete.vim. Plugin's author reply
> was: "Vim plugins cannot crash Vim. It seems if_lua garbage collection
> bug."
>
This sou
On Sunday, June 22, 2014 at 3:29:32 PM UTC-5, Ben Fritz wrote:
> The attached patch seems to fix the crash reported here:
>
> https://groups.google.com/d/topic/vim_dev/Nr8Ja4Zjghw/discussion
>
> The fix is simple in concept: any recursive call can be replaced with
> an explicit stack to "cheat" y
On Wednesday, January 21, 2015 at 8:00:27 PM UTC-6, James McCoy wrote:
> On Wed, Jan 21, 2015 at 02:32:29PM -0800, Sergey Vlasov wrote:
> > Since around last year I experience very frequent vim crashes. This is
> > caused by Lua written plugin neocomplete.vim. Plugin's author reply
> > was: "Vim pl
Comment #14 on issue 267 by fritzoph...@gmail.com: Segmentation fault with
if_lua (during or after the GC)
https://code.google.com/p/vim/issues/detail?id=267
I sort of doubt it's the same crash, but see if the patch for the other
garbage collection "set_ref" crash makes any difference:
ht
20 matches
Mail list logo
