Hi Ron!
On Fr, 31 Mai 2013, Ron Aaron wrote:
> I think there should be an option (probably an option, not a regex flag)
> which controls whether or not the engine finds "ff" (unicode 0xfb00) when
> searching for "f", for example. It seems to me that most people may not need
> it, but those of
On Fr, 31 Mai 2013, A. S. Budden wrote:
> > When using cscope, the path as provided to the "cs add" command is
> > used. If the working directory changes, this is potentially no longer
> > valid. This causes me a problem as I have a plugin that tries to
> > pause cscope and restart it (so it can
Here is an updated patch of the tagfunc feature from the old
vim_extended repository. I think, this has also been in the todo list
for very long:
,
| 8 Use a mechanism similar to omni completion to figure out the kind of tab
| for CTRL-] and jump to the appropriate matching tag (if the
Bram,
will this patch at least end up in todo.txt?
Mit freundlichen Grüßen
Christian
--
Wer nichts tut, kann nichts verändern.
-- Rolf Hasenclever
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
Bram,
On Do, 30 Mai 2013, Christian Brabandt wrote:
> Forwarding to vim-dev
>
> On Mi, 29 Mai 2013, Ben Fritz wrote:
>
> > I like the proposal by "glts" myself:
> >
> > > - ":set nonu nornu" means: I don't want any line numbers;
Bram,
gcc complains when compiling latest Vim version (7.3.1090) with
In file included from regexp.c:7864:0:
regexp_nfa.c: In function 'nfa_regpiece':
regexp_nfa.c:1390:19: warning: declaration of 'new_state' shadows a global
declaration [-Wshadow]
regexp_nfa.c:270:21: warning: shadowed declaratio
Bram,
here is a patch that fixes a bug with gn when the match is only a single
char width.
regards,
Christian
--
Die Ursache, die den Aberglauben hervorbringt, erhält und ernährt, ist
die Furcht.
-- Baruch de Spinoza (Tractatus theologico-politicus)
--
--
You received this mes
Hi Bram!
On So, 02 Jun 2013, Bram Moolenaar wrote:
> There is too much discussion about this. I think the current behavior
> is OK and does not have enough disadvantage to justify adding yet
> another option.
Note, that latest patch I sent, does not require an extra option, is
rather small, ma
Hi Bram!
On So, 02 Jun 2013, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > Bram,
> >
> > will this patch at least end up in todo.txt?
>
> I thought it was there, but I can't find it.
> Where is the patch?
It was attached to the mail, to w
On Sun, June 2, 2013 23:09, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>> here is a patch that fixes a bug with gn when the match is only a
>> single char width.
>
> Thanks! I'll put it in the todo list.
> Bonus points for writing a test.
Ha! I'll take t
On Sun, June 2, 2013 20:28, Yegappan Lakshmanan wrote:
> I am attaching a patch to add the :cdo and :ldo commands. The :cdo command
> can be used to execute commands over all the buffers in the quickfix list.
> The :ldo command can be used to execute commands over all the buffers in
> the location
On Sun, June 2, 2013 23:09, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>> On So, 02 Jun 2013, Bram Moolenaar wrote:
[variable tabstop patch]
>> > I thought it was there, but I can't find it.
>> > Where is the patch?
>>
>> It was attached to the
On Mon, June 3, 2013 16:02, Bram Moolenaar wrote:
> Eh, I said "author and date". I don't like puzzles. And I need the
> original author, not the person who resent someone else's work.
Ah, I misunderstood you. I think it startet here:
http://thread.gmane.org/gmane.editors.vim.devel/17469/focus=1
On Mon, June 3, 2013 16:40, Bram Moolenaar wrote:
> Eh, that post is from 2007. So which is the most recent one from the
> original author with the right patch?
I don't know, when Matthew posted the most recent patch.
As far as I know, Lech has updated the patch later, but it
went unnoticed by vi
On Mon, June 3, 2013 18:07, abud...@gmail.com wrote:
> Certainly looks promising: what do you think are the chances of getting
> this into Vim 7.4?
Looks pretty good I would say. From the latest todo list in the
repository:
Patch to store absolute path for cscope. (Christian Brabandt, 20
On Mon, June 3, 2013 17:42, Bram Moolenaar wrote:
> But let this not be an invitation for someone to do all this work,
> because I'm just going to add a line in the todo list and it will sit
> there for a while. At least until lots of bugs have been fixed before I
> dare including a feature that m
Hi Bram!
On Mo, 03 Jun 2013, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Sun, June 2, 2013 23:09, Bram Moolenaar wrote:
> > > Christian Brabandt wrote:
> > >> here is a patch that fixes a bug with gn when the match is only a
> > >&
On Mon, June 3, 2013 22:54, Matthew Winn wrote:
> On Mon, 3 Jun 2013 18:34:37 +0200, "Christian Brabandt"
> wrote:
>
>> Oh, well. I'll just carry it around for myself and keep working on it.
>> I already saw one problem, that when variable tabstops are enabled,
On Wed, June 5, 2013 00:14, Tony Mechelynck wrote:
> On 31/05/13 15:31, A. S. Budden wrote:
>>> When using cscope, the path as provided to the "cs add" command is
>>> used. If the working directory changes, this is potentially no longer
>>> valid. This causes me a problem as I have a plugin that
On Tue, June 4, 2013 18:29, Bram Moolenaar wrote:
>
> Patch 7.3.1112
> Problem:New regexp engine: \%V not supported.
> Solution: Implement \%V. Add tests.
> Files:src/regexp.c, src/regexp_nfa.c, src/testdir/test64.in,
> src/testdir/test64.ok
The good thing about this i
On Wed, June 5, 2013 08:56, Ingo Karkat wrote:
> On 05-Jun-2013 08:03 +0200, Christian Brabandt wrote:
>
>> [...] the old engine has an long standing bug with \%V ;(
>>
>> e.g:
>>
>> vim -u NONE -N
>> ifoobar
>> 0ve
>> /\%Vfoobar\%V
>>
On Thu, June 6, 2013 07:25, Marc Weber wrote:
> unpack into its own directory in tmp, then run the .sh script
> http://mawercer.de/tmp/test-case.zip
>
> using debugging, vim quits after the line
>
> -V20./log trace:
>
> line 1: let r = []
> line 2: for x2 in getqflist()
> line 3:
Bram,
when vim starts up, and some plugin opens the preview window, the cursor
will move to the preview window and not stay in the other window.
This can be seen here:
vim -u NONE -N --cmd 'pedit ~/.vimrc' foobar
Note, that the cursor is in the window with your $VIMRC and not in the
other one.
Hi Bram!
On Fr, 14 Jun 2013, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > Bram,
> > when vim starts up, and some plugin opens the preview window, the cursor
> > will move to the preview window and not stay in the other window.
> >
> > This
Hi Andy!
On So, 16 Jun 2013, Andy Wokula wrote:
> You said it will be confusing for the user. I don't think so.
> First: if 'vts' isn't set behind the scenes, the user won't notice
> anything.
> Second: if 'vts' is set behind the scenes, the user will notice some
> tabstop magic going on. The n
On So, 16 Jun 2013, Christian Brabandt wrote:
> Not good? Ok, here is the original patch again.
Sorry, left the test out. This one includes everything.
Mit freundlichen Grüßen
Christian
--
Wie man sein Kind nicht nennen sollte:
Charles Ton
--
--
You received this message from
On Mon, June 17, 2013 01:12, Bee wrote:
> g[lobal] with s[ubstitute]
>
> I used the following to replace ';' with '; ' only in lines with '}'
>
> It works, but if I want to stop early using 'q' it does not quit, I
> must use ^C.
>
> Also if I use 'a' to replace all, search/replace does not exit, ag
On Tue, June 18, 2013 09:46, Christian Brabandt wrote:
> On Mon, June 17, 2013 01:12, Bee wrote:
>> g[lobal] with s[ubstitute]
>>
>> I used the following to replace ';' with '; ' only in lines with '}'
>>
>> It works, but if I
Hi Tim!
On Di, 18 Jun 2013, Tim Chase wrote:
> On 2013-06-18 09:46, Christian Brabandt wrote:
> > On Mon, June 17, 2013 01:12, Bee wrote:
> > > Also if I use 'a' to replace all, search/replace does not exit,
> > > again needing ^C.
> > >
> >
On Tue, June 18, 2013 22:10, Bram Moolenaar wrote:
>> Attached is an updated patch, implementing your suggestions, as well as
>> a hit '?' to show a help banner.
>>
>> Bram, if this gets merged, I think it makes sense to also merge the 'u'
>> flag for undo the last substitution (that I have posted
Hi Zulox4!
On Do, 20 Jun 2013, Zulox4 wrote:
> On Saturday, May 25, 2013 8:17:36 PM UTC+2, v...@googlecode.com wrote:
> > Status: New
> >
> > Owner:
> >
> > Labels: Type-Defect Priority-Medium
> >
> >
> >
> > New issue 137 by zulolox4...@gmail.com: Memory fault-coredump unix aix
> >
>
Bram,
I noticed, findfile() leaks memory.
This patch fixes it:
iff --git a/src/eval.c b/src/eval.c
--- a/src/eval.c
+++ b/src/eval.c
@@ -10491,7 +10491,7 @@
{
do
{
- if (rettv->v_type == VAR_STRING)
+ if (rettv->v_type == VAR_STRING || rettv->v_type == VAR_
Hi Shane!
On Fr, 21 Jun 2013, Shane Thornton wrote:
> On Friday, June 21, 2013 7:45:26 AM UTC-7, Shane Thornton wrote:
> > If you type ":h z" and get to the commands starting with z there is
> > zH/zL missing from the list there. :)
>
> If I put my cursor on the C in that first sentence, then tr
On Fr, 21 Jun 2013, Christian Brabandt wrote:
> On Do, 20 Jun 2013, Markus Braun wrote:
>
> > I have a question about using wildcards in the path argument to findfile()
> > function. When running these commands
> >
> > mkdir -p "test/dir-1/" &&
On Fr, 31 Mai 2013, Christian Brabandt wrote:
> Here is an updated patch of the tagfunc feature from the old
> vim_extended repository. I think, this has also been in the todo list
> for very long:
>
> ,
> | 8 Use a mechanism similar to omni completion to figure o
Hi Shane!
On Sa, 22 Jun 2013, Shane Thornton wrote:
> On Saturday, June 22, 2013 12:55:29 AM UTC-7, Christian Brabandt wrote:
> > Hi Shane!
> >
> >
> >
> > On Fr, 21 Jun 2013, Shane Thornton wrote:
> >
> >
> >
> > > On
Hi Amadeus!
On Mo, 24 Jun 2013, Amadeus Demarzi wrote:
> I use `q` as my leader key, which means I have the following set in my vimrc:
>
> let mapleader="q"
> nnoremap q
> vnoremap q
> nnoremap Q q
> vnoremap Q q
>
> However, it seems on the newer builds of MacVim (specifically version 7.3
>
On Mon, June 24, 2013 23:54, Paul Maier wrote:
> Hi,
>
> the original vi on Sun took :su as :suspend,
> whereas vim takes :su as :substitute.
>
> I am very used to typing :su.
>
> Would it be possible for VIM 7.4 to add a new compatibility flag to
> cpoptions
> about the meaning of :su ?
>
> sugges
On Tue, June 25, 2013 13:16, Tony Mechelynck wrote:
> On 25/06/13 11:15, Christian Brabandt wrote:
>> On Mon, June 24, 2013 23:54, Paul Maier wrote:
>>> Hi,
>>>
>>> the original vi on Sun took :su as :suspend,
>>> whereas vim takes :su as :sub
Hi sxc4244!
On Di, 25 Jun 2013, sxc4...@g.rit.edu wrote:
> On Thursday, May 30, 2013 2:31:11 AM UTC-4, Nazri wrote:
> > On Wed, Feb 6, 2013 at 11:06 PM, Bram Moolenaar wrote:
> >
> > > No, I don't want to remove or deprecate existing options. It's very
> >
> > > annoying for people who get a
On Mon, July 1, 2013 17:45, Ingo Karkat wrote:
> Hello Vim developers,
>
> I noticed a regression:
>
> $ vim -N -u NONE
> :echo "foo"
> " The intro message is cleared, the (now empty) UI does not show "foo".
> " Expected behavior: The intro message stays visible, the command-line
> shows "foo".
>
>
On Tue, July 2, 2013 09:26, Ingo Karkat wrote:
> Correct, this doesn't happen in GVIM, and also doesn't happen in the
> Windows console version, only in a Linux terminal.
What is your terminal, your $TERM variable and what does vim set the term
option to?
As I said, I don't see it neither on scre
Hi Christian!
On Do, 04 Jul 2013, Christian J. Robinson wrote:
>
> At some point in the last couple of weeks I have noticed that my
> recent Vim builds (native Windows 7 binaries built under cygwin) are
> crashing whenever my custom 'balloonexpr' is triggered--the balloon
> shows, then Vim crash
Hi Bailey!
On Mi, 03 Jul 2013, Bailey Ling wrote:
> Hey all,
>
> I'm running into a weird issue with rendering the statusline in my plugin
> vim-airline. I created a minimal vimrc gist here
> (https://gist.github.com/bling/7d26e6c63ba0207e657f) that illustrates the
> problem.
>
> It appears
On Fr, 05 Jul 2013, Christian Robinson wrote:
> On Jul 5, 2013, at 2:46 AM, Christian Brabandt wrote:
> > On Do, 04 Jul 2013, Christian J. Robinson wrote:
> >> At some point in the last couple of weeks I have noticed that my
> >> recent Vim builds (native Windows 7
gt; Solution: Make a wildcard work properly. (Christian Brabandt)
> > Files: src/misc2.c, src/testdir/test89.in, src/testdir/test89.ok
> >
>
> With this patch, upward search fails when search is started from
> non-existing directory.
>
> Steps To Reproduce:
&
On Tue, July 9, 2013 15:15, Dimitar DIMITROV wrote:
> Hi list,
>
> 1. vim -nNX -u NONE
> 2. :se ve=all
> 3. 3otest
> 4. g$
>
> Then I expect k to move me up in the same column but it goes at $ in the
> previous line.
>
> Note: in step 4 if I move to g$ using l then k moves the cursor
> corr
On Thu, July 11, 2013 17:36, Ben Fritz wrote:
> On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote:
>>
>> Perhaps we can somehow detect that CTRL-R = had the side effect of
>>
>> changing the text and then split undo. When it only returns the text to
>>
>> be inserted, there is no ne
On Thu, July 11, 2013 17:41, Benjamin Fritz wrote:
> On Thu, Jul 11, 2013 at 10:36 AM, Ben Fritz
> wrote:
>> On Thursday, July 4, 2013 4:44:26 AM UTC-5, Bram Moolenaar wrote:
>>>
>>> Perhaps we can somehow detect that CTRL-R = had the side effect of
>>>
>>> changing the text and then split undo.
On Do, 11 Jul 2013, Travis wrote:
> I noticed in the vim 7.4a beta (I believe it is the patch 7.3.787 but I'm not
> entirely sure), it looks like relative line number performance has greatly
> decreased.
>
> If I open a file with just 100 lines, scrolling via rnu is quite choppy, and
> if I tu
Bram,
this small patch makes sign placement easier by defaulting to use the
current buffer instead of yielding an error.
Mit freundlichen Grüßen
Christian
--
Morgens am Frühstückstisch. Er kratzt mit dem Löffel das Eigelb von
seinem Hemd und sagt: "Oh Mann, ich sehe aus wie ein Schwein!"
Sie: "S
On Fri, July 12, 2013 01:10, Sumonto Ghosh wrote:
> Hi,
> Wondering if anyone could help me debug why "bd" would close gvim even if
> multiple buffers are open.
> I does not close the specific buffer.
>
> I have the following plugins installed:
> solarized
> nerdtree
> taglist_46
Well, please be a
Bram,
attached patch fixes this issue from the todo list:
,
| When 'foldmethod' is "indent", using >> on a line just above a fold
| makes the cursor line folded. (Evan Laforge, 2009 Oct 17)
`
regards,
Christian
--
Nach 10 Uhr müssen alle Ki
function) it can't find s:foo.
`
,
| When a script contains "redir => s:foo" but doesn't end redirection, a
| following "redir" command gives an error for not being able to access s:foo.
| (ZyX, 2011 Mar 27)
`
,
| Patch to fix \%V item in
On Mon, July 29, 2013 14:59, Dimitar DIMITROV wrote:
>> Hi all,
>>
>> Not sure why /\_.* matches at every line Vs only once...
>> I would expect a single match at start of file because \_. matches any
>> char including end of line and * is greedy
>> /pattern\_.* does what I expect: it matches from
On Mon, July 29, 2013 16:14, Dimitar DIMITROV wrote:
>> >> Hi all,
>> >>
>> >> Not sure why /\_.* matches at every line Vs only once...
>> >> I would expect a single match at start of file because \_. matches
>> any
>> >> char including end of line and * is greedy
>> >> /pattern\_.* does what I exp
Hi Ingo!
On Fr, 26 Jul 2013, Ingo Karkat wrote:
> Hello Vim developers,
>
> Patch 7.3.590 allows to set the visual selection directly via the marks
> '< and '>. I've found a problem with :set selection=exclusive (while
> developing a custom mapping): When the first selection after Vim startup
>
Hi Mike!
On So, 21 Jul 2013, Mike Williams wrote:
> On 20/07/2013 10:13, LCD 47 wrote:
> > I believe this can be fixed with a counter that means something
> >along the lines of: "this line is longer than &tw, and it has no
> >breaking point for the first X characters". Then X would be update
On Mi, 24 Jul 2013, Jeroen Budts wrote:
> I have a feature request for gvim, I'm not sure if I should ask it
> here or on the dev list?
> Would it be possible to add support for strikethrough text in Gvim?
> Since gvim can already display bold, italic, underline and undercurl
> text I guess it can
On Tue, July 16, 2013 16:57, Benjamin Fritz wrote:
> Eric Van Dewoestine found this while investigating an eclim issue I was
having.
> When 'autochdir' is set, calling setbufvar() changes Vim's current
directory to that of the buffer having its variable set. I think this
should not happen.
> Reprod
On Mon, July 29, 2013 19:32, Seungbeom Kim wrote:
> The 'equalalways' option makes all the windows the same size after a
window is split or closed. However, it doesn't when the Vim window
(either
> the terminal or the GUI) is resized. I hear many people run [g]vimdiff
or
> ':vsplit', enlarge the Vi
On Wed, July 31, 2013 17:17, Ben Fritz wrote:
> A while ago there was a similar problem where :vimgrep was causing
> directory changes due to 'autochdir'. The fix for :vimgrep also had to
> deal with autocmds which might change the directory.
Are you talking about issue 72? As far as I know, this
Hi Bram!
On Mi, 31 Jul 2013, Bram Moolenaar wrote:
>
> [Christian, for some reason quoted long lines are wrapped badly]
Yeah, Squirrelmail messed it up. I usually reformat mails using Vim (of
course! ;)), but forgot this time.
[adjust Vim windows, when vim is resized and 'equalalways' is set]
On Fri, August 2, 2013 04:46, richard emberson wrote:
> Interesting ...
>
> If you define a file XXX with the content:
> vv
> 1
> 2
> 3
> 4
> 5
> 6
> 7
> 8
> 9
>
> function! Load()
>let list = [
> \ {
> \ 'filename': 'XXX',
> \ 'lnum': 2,
> \ 'col': 5,
Hi Benjamin!
On Di, 06 Aug 2013, Benjamin R. Haskell wrote:
> On Tue, 6 Aug 2013, Ben Fritz wrote:
>
> >On Tuesday, August 6, 2013 11:21:02 AM UTC-5, Benjamin R. Haskell wrote:
> >>On Tue, 6 Aug 2013, Dimitar DIMITROV wrote:
> >>
> >>>Hi all,
> >>
> >>>If you open the latest vim (vim -nNX -u NON
Hi Gary!
On Do, 08 Aug 2013, Gary Johnson wrote:
> The following problem appears in vim 7.3.882 and 7.4b.19 on Linux.
>
> In the Vim src directory, in an 80x24 terminal, execute the
> following.
>
> vim -N -u NONE -c 'r !ls' +0 -c 'syn on' -c 'syn match Error /\.c\zs\n.*/'
>
> Scroll down
On Do, 08 Aug 2013, glts wrote:
> When I run an external command like :!find I can see the output in the
> messages area and the prompt
>
> Press ENTER or type command to continue
>
> By reflex I hit "u" to scroll up and I got
>
> Press ENTER or type command to continuePress ENTER or type comma
Bram,
I had a problem with the NrrwRgn Plugin that seems to hang vim.
Debugging it, I could make vim hang with this input:
vim -N -c 'try|noa sview $VIMRUNTIME/doc/options.txt|finally |bw|endtry
(It seems my .vimrc interferes, not sure which setting does).
This hangs in buffer.c
,
|
On Sa, 10 Aug 2013, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>
> > I had a problem with the NrrwRgn Plugin that seems to hang vim.
> > Debugging it, I could make vim hang with this input:
> >
> > vim -N -c 'try|noa sview $VIMRUNTIME/doc/options.txt|f
On Sa, 10 Aug 2013, Gary Johnson wrote:
> On 2012-08-05, Christian Brabandt wrote:
>
> > Does this patch work for you?
> >
> > diff --git a/src/spell.c b/src/spell.c
> > --- a/src/spell.c
> > +++ b/src/spell.c
> > @@ -10155,9 +10155,24 @@
&g
Hi Gary!
On So, 11 Aug 2013, Gary Johnson wrote:
> Christian,
>
> On 2013-08-11, Christian Brabandt wrote:
> > On Sa, 10 Aug 2013, Gary Johnson wrote:
>
> > > Now that 7.4 has been released and we can resume considering
> > > features instead of just bug fi
On Fr, 09 Aug 2013, Ben Fritz wrote:
> On Friday, August 9, 2013 11:20:37 AM UTC-5, Dimitar DIMITROV wrote:
> > >I don't see anything wrong. For me it selects all text from the opening {
> > >to the closing }. What do you
> > see?
> > >
> > >I tried gvim 7.3.822 on Windows, and also vim (not gvi
On Do, 08 Aug 2013, Dimitar DIMITROV wrote:
> As per the subject :)
Can you check, whether the attached patch fixes it for you?
regards,
Christian
--
Was die Welt in diesem Augenblick sucht, ist viel weniger ein
Gleichgewicht als eine Sprache.
-- Jean Giraudoux
--
--
You rece
On Fr, 09 Aug 2013, Gary Johnson wrote:
> In your video, you paged forward and back using ^F and ^B. I just
> tried that and it works for me, too. However, scrolling forward and
Ah, from your initial description it wasn't clear to me, that scrolling
actually means using up/down and not paging
On Tue, August 13, 2013 01:00, Einar Lielmanis wrote:
> Encrypted file contents are destroyed, if something (e.g autocmd)
> triggers write event, while user is being asked for password.
>
> To repro:
> 1. have an encrypted.txt ready (:X)
> 2. gvim, :au focuslost * w
> 3. :e encrypted.txt, don't typ
Hi Péter!
On Mi, 14 Aug 2013, Péter Kasza wrote:
> Dear vim_dev list!
>
> I've been using the tslime plugin for some time now, but after an update it
> somehow doesn't seem to work anymore. The call to system("tmux load-buffer
> -", buf) hangs forever. I can make it work by changi
On Di, 13 Aug 2013, Christian Brabandt wrote:
> On Tue, August 13, 2013 01:00, Einar Lielmanis wrote:
> > Encrypted file contents are destroyed, if something (e.g autocmd)
> > triggers write event, while user is being asked for password.
> >
> > To repro:
> > 1
On Thu, August 15, 2013 14:57, Dimitar DIMITROV wrote:
> Hi all,
>
> I've noted this behaviour with omaps: in my omap I jump to a place in the
> buffer, then after an if test I select visually something. So all is good
> when
> the test succeds and only the visual area gets modified. Now if the tes
On Thu, August 15, 2013 15:53, Dimitar DIMITROV wrote:
>>> Hi all,
>>>
>>> I've noted this behaviour with omaps: in my omap I jump to a place in
>>> the
>>> buffer, then after an if test I select visually something. So all is
>>> good
>>> when
>>> the test succeds and only the visual area gets modi
On Do, 15 Aug 2013, Matt Yoder wrote:
> FWIW I too have segfaults with ruby syntax on, 7.4, os x 10.6.8.
> Updating my vim syntax file resolved the problem.
Well, 7.4.003 should have fixed that. Can you confirm?
regards,
Christian
--
Durch die Leidenschaften lebt der Mensch, durch die Vernunft
On Fr, 16 Aug 2013, Péter Kasza wrote:
> > custom .vimrc and no plugins loaded)?
> Yep, tried a simple echo system("tmux load-buffer -", "asdf") without
> vimrc/plugins and the same freeze happened.
I don't see this.
regards,
Christian
--
Gott hat auch die Dummheit geschaffen, aber er hat sie
On Mon, August 19, 2013 11:30, John Beckett wrote:
> Dimitar DIMITROV wrote:
>> Now try :ec getpos('.') -> [0, 4, 17, 0]
>> Move away and :call setpos('.',[0,4,17,0])
>> If you use k or j you will not move just
>> above/below the char but in some weird location
>
> Say the cursor is in column 20,
On Do, 15 Aug 2013, Bram Moolenaar wrote:
> Christian Brabandt wrote:
> > Wouldn't it be a good idea, to have the file set readonly for as long it
> > hasn't been encrypted (e.g. the current windows behaviour)?
>
> You mean, until it has been decrypted. That
Hi Jesus!
On So, 18 Aug 2013, Jesus Antonio Santos Giraldo wrote:
> Not to mention that there is already a patch for it... :(
All whitespace as something different? Can't you use the conceal feature
for that?
:syn match MyWhitespace /\s/ conceal cchar=_ containedin=ALL
:setl conceallevel=2 con
On Mo, 19 Aug 2013, Christian Brabandt wrote:
> May be another optional parameter to the setpos() function, that
> if given specifies the desired cursor position?
Like the attached patch does.
regards,
Christian
--
Es gehört viel dazu, eine Brücke hinter sich abzureißen, wenn man auch
On Tue, August 20, 2013 09:02, Ingo Karkat wrote:
> Note that concealing has to extend the existing syntax, which can break
> it.
Well changing the syntax rules is of course a way of breaking it, but
I think it should work well enough most of the times. And while I am not
very proficient with synt
Hi Marius!
On Di, 20 Aug 2013, Marius Gedminas wrote:
> Vim 7.4 broke my svn filetype plugin (http://mg.pov.lt/vim/ftplugin/svn.vim).
>
> The plugin opens a new split window and puts the output of 'svn diff' in
> there when I run 'svn commit'. This window gets some attributes set,
> including '
On Thu, August 22, 2013 07:40, Marius Gedminas wrote:
> On Tue, Aug 20, 2013 at 05:15:49PM +0200, Christian Brabandt wrote:
>
>
> Your patch fixes the bug, thanks!
>
> What are the next steps to get it included upstream?
Bram will include it eventually.
regards,
Christian
--
On Thu, August 22, 2013 17:23, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>> On Mo, 19 Aug 2013, Christian Brabandt wrote:
>>
>> > May be another optional parameter to the setpos() function, that
>> > if given specifies the desired cursor position?
&
On Do, 22 Aug 2013, Nikolay Pavlov wrote:
> I bet there is a bunch of scripts using 4-variable lets. Simple grep over
What do you mean with 4-variable lets?
> the mess in $HOME/.vam (I hold all but my plugins there) found at least
> LaTeX_box plugin (ftplugin/latex-box/common.vim) and python-mo
[redirected to vim-dev, it is better suited there]
On Do, 22 Aug 2013, Andrew Stewart wrote:
> On 21 Aug 2013, at 19:05, Josh wrote:
> > This is already a feature
> > request:https://code.google.com/p/vim/issues/detail?id=117&q=Sign .
Bram,
attached patch adds a 'signcolumn' option, that let's
On Mi, 21 Aug 2013, Dimitar DIMITROV wrote:
> Tested with the latest version of Vim from Mercurial.
> After a * search, then cgn and then . to repeat it for all matches,
> I cannot continue past the end of file and change any matches before my
> initial position
Try the attached patch.
regards,
On Do, 22 Aug 2013, Bohr Shaw wrote:
> However, the document says the register "1 always hold the text
> deleted by the delete operator with these movement commands:|%|, |(|,
> |)|, |`|, |/|, |?|, |n|, |N|, |{| and |}|.
I think the help is clear here.
,[ :h quote1 ]-
| Numbered register 1
Bram,
this patch adds a digraph function. This allows plugin writers to
generate needed digraphs easily and one does not need such a crude
workaround anymore:
:exe ":norm! :let x = '\a:'\"
regards,
Christian
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type y
On Do, 22 Aug 2013, Bram Moolenaar wrote:
> Christian Brabandt wrote:
>
> > Bram,
> > this patch adds a digraph function. This allows plugin writers to
> > generate needed digraphs easily and one does not need such a crude
> > workaround anymore:
>
following thread:
> Wrong completion entry selection after backspace
> https://groups.google.com/d/topic/vim_dev/AcTTNQzfB2o/discussion
> In this thread, Christian Brabandt sent two patches, and the first patch
> has this problem. The second patch didn't have such problem and it
On Sa, 07 Sep 2013, Gary Johnson wrote:
> On 2013-08-12, Gary Johnson wrote:
> > On 2013-08-12, Christian Brabandt wrote:
>
> > > Oh well, here is an updated version attached. Yes, it is really
> > > attached...
> >
> > I'm glad to have the update
On Mon, September 9, 2013 12:31, Mike Williams wrote:
> On 09/09/2013 10:56, Nikolay Pavlov wrote:
>> On Sep 9, 2013 1:40 PM, "Mike Williams"
>>
>> wrote:
> I had tried calls to escape(..., '\') and that made no difference.
Where did you do that? You need to make sure, that you only escape
the ri
On Wed, September 11, 2013 14:07, Dmitry Frank wrote:
> So, is this issue fixed now? If yes, then which patch should fix it?
7.4.018
regards,
Christian
--
--
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 inf
On Wed, September 11, 2013 13:43, jan.stoc...@t-online.de wrote:
> Hi,
>
> if you read with
>
> - Vim 7.4.22 (32bit)
>
> - Windows 7 (x64)
>
> from a command line output by
>
> :[range]r[ead] [++opt] !{cmd}
>
> and using parenthesis the command is completly broke
1 - 100 din 7064 matches
Mail list logo
