headers
Nazri Ramliy | 1 Feb 2009 10:12
Picon
Gravatar

[TOY PATCH]: todo.txt:8 For ":find" and ":sfind" expand files found in 'path'

Hello all,

That entry in todo.txt has been the source of my itch for quite some time.

I had resorted to writing custom zsh command line completion for
completing files found in my .vimrc path setting to start vim with.

That means to comfortably find and edit any file in my path setting I
have to drop down to the command line.

With this patch that the itch is gone, at least for me.

What works: expanding files found in path for simple path settings
(absolute and relative)

What does not work: it does not grok path_extra-specific thingy.

I'm sure I have overlooked hundreds of issues while patching it hence
the 'TOY PATCH' :)

The patch is against the latest pull from repo.or.cz's vim repository.
Patch it with -p1 from your ~/src/vim.

nazri.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nazri Ramliy | 1 Feb 2009 10:28
Picon
Gravatar

Re: [TOY PATCH]: todo.txt:8 For ":find" and ":sfind" expand files found in 'path'

On Sun, Feb 1, 2009 at 5:12 PM, Nazri Ramliy <ayiehere <at> gmail.com> wrote:
> Hello all,
> The patch is against the latest pull from repo.or.cz's vim repository.
> Patch it with -p1 from your ~/src/vim.

Eek! Please use this patch instead as the previous one contains two
unnecessary hunks that modified misc2.c and os_msdos.c (hehe).

Now I'll go back to my cave.

nazri.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
Attachment (expand_files_for_find_sfind.2.patch): text/x-diff, 4160 bytes
Permalink | Reply | 0 comments |
headers
François Ingelrest | 1 Feb 2009 10:35
Picon

Re: Tabline not refreshed when using :saveas

Hi,

On Wed, Nov 12, 2008 at 13:08, Bram Moolenaar wrote:
> Francois Ingelrest wrote:
>
>> Hi all,
>>
>> When I do the following:
>>  1. vim -u NONE -U NONE foo.c
>>  2. :tabnew
>>  3. :tabprev
>>  4. :saveas bar.c
>>
>> The tabline is not refreshed, and the current tab is still named
>> foo.c. Switching to the other tab correctly refreshed the first tab,
>> which is then renamed bar.c (as expected).
>>
>> This is with Vim 7.2.30 on Ubuntu 8.10.
>
> One more for the todo list...

Here's a patch that hopefully fixes this bug.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
Attachment (saveas_tabline.diff): text/x-patch, 769 bytes
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bram Moolenaar | 1 Feb 2009 14:44
Picon

Re: Tabline not refreshed when using :saveas


Francois Ingelrest wrote:

> >> Hi all,
> >>
> >> When I do the following:
> >>  1. vim -u NONE -U NONE foo.c
> >>  2. :tabnew
> >>  3. :tabprev
> >>  4. :saveas bar.c
> >>
> >> The tabline is not refreshed, and the current tab is still named
> >> foo.c. Switching to the other tab correctly refreshed the first tab,
> >> which is then renamed bar.c (as expected).
> >>
> >> This is with Vim 7.2.30 on Ubuntu 8.10.
> >
> > One more for the todo list...
> 
> Here's a patch that hopefully fixes this bug.

Thanks.  I'll have a closer look later.

--

-- 
hundred-and-one symptoms of being an internet addict:
37. You start looking for hot HTML addresses in public restrooms.

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 1 Feb 2009 14:44
Picon

Re: PATCH: tab line redrawn when 'bomb' is set


Lech Lorens wrote:

> The attached patch causes the tab line to be redrawn with + indicating a
> change to a file whenever 'bomb' is set.

Thanks!

--

-- 
hundred-and-one symptoms of being an internet addict:
35. Your husband tells you he's had the beard for 2 months.

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Bram Moolenaar | 1 Feb 2009 14:44
Picon

Re: PATCH: changing 'guifont' in console does not cause an unnecessary screen redraw


Lech Lorens wrote:

> The attached patch gets rid of the unnecessary screen redraw when
> 'guifont', 'guifontset' or 'guifontwide' is set in Vim running in a
> console.

Thanks!  Looks OK, except that I usually avoid variables with a negative
name, as this leads to double negatives: "!dont_check".  Using
"check_redraw" with default TRUE is simpler.

--

-- 
hundred-and-one symptoms of being an internet addict:
34. You laugh at people with 14400 baud modems.

 /// Bram Moolenaar -- Bram <at> Moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Markus Heidelberg | 3 Feb 2009 15:09
Picon

Re: A branch for join_O(n) patches was: Re: [patch] Re: make joining lines O(n)


Markus Heidelberg, 23.01.2009:
> Milan Vancura, 22.01.2009:
> > I vote for fix/fast_join. It is a fix, not a feature, I think.
> > Feature == new option or something like that. This is a fix of the slow
> > algorithm. I know that better word would be "an improvement" but in case I have
> > just three words I must match in (fix, feat, dev), I vote for fix.
> 
> Yes, it's a fix. I rather thought about the two namespaces to
> distinguish between fast-forward and rebase-able branches. I didn't want
> to get too many namespaces and I think, since fixes should go upstream,
> it doesn't make too much sense. But on the other hand I think it's OK,
> we can put upstream stuff into vim_extended to get it mature till
> inclusion. So we could have "fix" and "feat" with non-rebasing policy
> and "dev" for everything one can dream of.
> 
> > Adding me to the project: my name at repo.cz is 'milan', so you can add me to
> > your project. Thank you.
> 
> OK, I will do it in the near future and send you a mail then.

Sorry for the delay. I have finally added the README to the stuff
branch and renamed the feature branches.
Now you have push access, Milan. You can create the fix/fast-join
branch. Note the dash instead of an underscore, I tend to like it more,
it's also easier to type.

Just some guidelines, I haven't put them into the README yet:
- Only fast-forward pushes to your branch.
- The 'vim' branch is the branch to be merged into fix/fast-join. I can
(Continue reading)

Permalink | Reply | 0 comments |
headers
zlel | 3 Feb 2009 12:51
Picon

How to do dynamic syntax highlighting


Cross reference multiple search patterns dynamically.
You need vim 7.0 and above for this but it comes in handy.
Convert ^R and ^M to their equivalent control codes or grab the mime64
from the bottom of the mail.

:if (!exists("g:hicount"))
	:let g:hicount=0
	:let g:hilite = {}
	:hi M0 guibg=red
	:hi M1 guibg=green
	:hi M2 guibg=blue
	:hi M3 guibg=cyan
	:hi M4 guibg=magenta
	:hi M5 guibg=yellow
	:hi M6 guibg=gray
	:hi M7 guibg=orange
	:hi M8 guibg=purple
	:hi M9 guibg=violet
	:hi M10 guibg=red
	:hi M11 guibg=green
	:hi M12 guibg=blue
	:hi M13 guibg=cyan
	:hi M14 guibg=magenta
	:hi M15 guibg=yellow
	:hi M16 guibg=gray
	:hi M17 guibg=orange
	:hi M18 guibg=purple
	:hi M19 guibg=violet
:endif
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ingo Karkat | 4 Feb 2009 00:35
Picon
Favicon
Gravatar

Re: How to do dynamic syntax highlighting


On 03-Feb-09 12:51, zlel wrote:
> Cross reference multiple search patterns dynamically.
> You need vim 7.0 and above for this but it comes in handy.
> Convert ^R and ^M to their equivalent control codes or grab the mime64
> from the bottom of the mail.
> ...

There's a plugin named mark.vim 
(http://www.vim.org/scripts/script.php?script_id=1238) that does this, too. (And 
it provides many useful mappings, etc.) Have you seen it?

-- regards, ingo

-- 
   -- Ingo Karkat -- /^-- /^-- /^-- /^-- /^-- /^-- http://ingo-karkat.de/ --
--

-- 
	Through trail an error, I finally managed to write a signature.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Andreas Bernauer | 4 Feb 2009 11:08
Picon
Favicon

Bug in gvim: diffpatch can't handle reversed patches

Hi,

when I apply a reversed patch on an open file with 'diffpatch', gvim opens a
window with an empty buffer instead of the patched file. 'godlygeek' on IRC
suggested reporting this bug on this mailing list.

It seems, gvim automatically answers the questions from the patch program
'Reversed (or previously applied) patch detected!  Assume -R? [n]'
and
'Apply anyway? [n] '
with the default answer for me (as if I pressed 'Enter'), resulting in the empty
buffer.

I expected to be able to answer the questions myself :-) as it happens in vim.

How to reproduce:
- Have two files which differ, e.g. each contains a single but different line
  (eg., see attached files 'text' and 'text-new')
- Create patch:
  $ diff text text-new > patch
- Start vim with the newer file
  ./vim-7.2 -u NONE -U NONE -i NONE --noplugin -N -g text-new
- in gvim, try to apply patch file:
  :diffpatch patch

Result is empty file instead of (reversely) patched file because gvim does not
allow me to answer patch questions 'Assume -R?' and 'Apply anyway?'.

Note, the bug only appears if gui (-g) AND non-compatible mode (-N) are enabled.
If not in gui mode, the bug never appears (either compatible or non-compatible
(Continue reading)

Permalink | Reply | 4 comments |

Gmane