On Sun, May 10, 2015 at 6:47 PM, Daniel Hahler
google-groups+2...@thequod.de wrote:
I think it would be great if the Zsh options would be in the zsh syntax file,
which would also allow for them to be used through syntaxcomplete#Complete.
I am attaching a patch for this, but am unsure if it's
On Sat, Mar 12, 2011 at 00:08, Nikolai Weibull n...@bitwi.se wrote:
On Wed, Mar 2, 2011 at 18:34, ZyX zyx@gmail.com wrote:
The following patch adds foldexpr option that will fold sections separated by
sequences of `=' (foldlevel=1) and `-' (foldlevel=2).
What’s the general practice
On Sat, Apr 2, 2011 at 22:15, Nikolai Weibull n...@bitwi.se wrote:
On Sat, Apr 2, 2011 at 20:09, Thilo Six t@gmx.de wrote:
you are listed in readline.vim as maintainer.
Since readline.vim has been lastly updated readline has gained new features,
therefor i have updated the listed keywords
On Fri, Mar 11, 2011 at 16:56, Ben Fritz fritzophre...@gmail.com wrote:
On Mar 11, 1:44 am, Nikolai Weibull n...@bitwi.se wrote:
On Thu, Mar 10, 2011 at 17:15, Ben Fritz fritzophre...@gmail.com wrote:
On Mar 8, 5:13 am, Nikolai Weibull n...@bitwi.se wrote:
Also, I don’t understand what
On Wed, Mar 2, 2011 at 18:34, ZyX zyx@gmail.com wrote:
The following patch adds foldexpr option that will fold sections separated by
sequences of `=' (foldlevel=1) and `-' (foldlevel=2).
What’s the general practice for this? Do we set foldexpr from
ftplugin files, or is that up to the user
On Wed, Dec 1, 2010 at 22:00, Nikolai Weibull n...@bitwi.se wrote:
On Wed, Dec 1, 2010 at 21:12, Bram Moolenaar b...@moolenaar.net wrote:
Nikolai Weibull wrote:
Writing “Let’s begin …” marks the ‘s’ as a spelling
error. Writing “Let's begin …” works fine. Is this a bug,
or am I missing
2011/1/7 Adrien Axioplase Piérard axioplase+vim...@gmail.com:
Also, it may help *a lot* too to colour blocks of consecutive related
digraphs in similar colours, such as all maths symbols, all
Japanese symbols, all Greek letters and so on.
Wouldn’t it be better to use proper headers for each
On Fri, Jan 7, 2011 at 20:25, David J. Hamilton gro...@hjdivad.com wrote:
Excerpts from Nikolai Weibull's message of Fri Jan 07 00:05:10 -0800 2011:
Color is seldom the answer.
I have to strongly disagree.
Right back at you.
Either way, the proper solution is the one I mentioned, by
Hi!
The jumplist size is currently, per the documentation, fixed at 100
entries. It would be great if the size was configurable. Believe it
or not, but I want to lower it. I would like to set the jumplist size
to the number of lines in my terminal so that I can avoid the “more”
prompt.
--
On Wed, Dec 8, 2010 at 13:41, Bram Moolenaar b...@moolenaar.net wrote:
Nikolai Weibull wrote:
The jumplist size is currently, per the documentation, fixed at 100
entries. It would be great if the size was configurable. Believe it
or not, but I want to lower it. I would like to set
On Tue, Nov 30, 2010 at 21:11, Bram Moolenaar b...@moolenaar.net wrote:
Nikolai Weibull wrote:
Writing “Let’s begin …” marks the ‘s’ as a spelling
error. Writing “Let's begin …” works fine. Is this a bug,
or am I missing something?
You are using weird quotes from cp1252. The spell
On Wed, Dec 1, 2010 at 12:05, Mike Williams
mike.willi...@globalgraphics.com wrote:
If the spell lists are in 7-bit ASCII then applying a Unicode to ASCII
conversion should map U+2019 to U+0027 and make spell DWIM.
What do you mean by ”applying a Unicode to ASCII conversion”?
--
You received
On Wed, Dec 1, 2010 at 21:12, Bram Moolenaar b...@moolenaar.net wrote:
Nikolai Weibull wrote:
Writing “Let’s begin …” marks the ‘s’ as a spelling
error. Writing “Let's begin …” works fine. Is this a bug,
or am I missing something?
You are using weird quotes from cp1252. The spell
Writing “Let’s begin …” marks the ‘s’ as a spelling error. Writing
“Let's begin …” works fine. Is this a bug, or am I missing something?
--
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 information, visit
On Sun, Nov 28, 2010 at 21:10, Rogutės Sparnuotos
rogu...@googlemail.com wrote:
You are listed as the Maintainer of a vim syntax file syntax/logindefs.vim,
so I am sending you the attached patch with the hope that you will either
commit the changes or forward them to an appropriate place.
Hi!
On Tue, Sep 14, 2010 at 03:23, forbin colossus.for...@gmail.com wrote:
On Sep 1, 10:54 am, ZyX zyx@gmail.com wrote:
I have written a syntax file for YAML markup language that has the following
differencies with runtime/syntax/yaml.vim from mercurial repository:
You might also want to
On Wed, Sep 1, 2010 at 19:54, ZyX zyx@gmail.com wrote:
I have written a syntax file for YAML markup language that has the following
differencies with runtime/syntax/yaml.vim from mercurial repository:
Great! Please consider taking over maintenance of this file. Bram,
if ZyX wants to
Can someone who was involved in the addition of changelog_entry_prefix
please look at this. I can’t remember what the deal was. Thanks!
(The version in the Mercurial repository has the correct date, by the way.)
-- Forwarded message --
From: Alexandre Fournier
On Sat, Jul 24, 2010 at 05:06, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 23/07/10 20:06, Nikolai Weibull wrote:
meta/ may actually appear anywhere in the document, if places is
referring to HTML processors (which of course don’t have to respect
it).
meta in an HTML document
On Sat, Jul 24, 2010 at 14:57, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 24/07/10 10:55, Nikolai Weibull wrote:
As near the top as possible: how could that have eluded you?
It hasn’t, and the fact that we’re discussing a moot point hasn’t either.
--
You received this message
Bram Moolenaar wrote:
Patrick Texier wrote:
No, it is the right way to define encoding of a 8-bit file. Vim can not
choose between ISO-8859-1(15), cp1252, cp1250...
I'm trying to think of a valid reason to change
'fenc' in the modeline. Can't think of one...
Oh, wait, the order is wrong,
On Fri, Jul 23, 2010 at 17:22, Benjamin R. Haskell v...@benizi.com wrote:
As Bram asserted, modelines take effect too late to serve this purpose.
Then the modeline needs to take effect earlier to serve this purpose.
--
You received this message from the vim_dev maillist.
Do not top-post! Type
On Fri, Jul 23, 2010 at 19:04, James Vega james...@jamessan.com wrote:
On Fri, Jul 23, 2010 at 12:56 PM, Nikolai Weibull n...@bitwi.se wrote:
On Fri, Jul 23, 2010 at 17:22, Benjamin R. Haskell v...@benizi.com wrote:
As Bram asserted, modelines take effect too late to serve this purpose
On Fri, Jul 23, 2010 at 19:33, James Vega james...@jamessan.com wrote:
On Fri, Jul 23, 2010 at 1:25 PM, Nikolai Weibull n...@bitwi.se wrote:
Sort of like a modeline?
Sort of, except modelines can be at the top or the bottom of the file
And one could easily scan from the beginning or end
On Thu, May 27, 2010 at 17:23, Ben Fritz fritzophre...@gmail.com wrote:
On May 26, 7:32 am, Tony Mechelynck antoine.mechely...@gmail.com
wrote:
As for floating point numbers, I constantly use Vim as a floating-point
calculator; I wouldn't say it's a useless feature. Not a /necessary/ one
--
On Sat, May 22, 2010 at 09:15, cyril romain cyril.rom...@gmail.com wrote:
On Mon, Nov 30, 2009 at 10:42 AM, Nikolai Weibull n...@bitwi.se wrote:
On Sun, Nov 29, 2009 at 09:55, cyril romain cyril.rom...@gmail.com
wrote:
Here is a patch for yaml syntax highlighting.
I’ll review it.
Any
On Wed, May 26, 2010 at 09:52, Nikolai Weibull n...@bitwi.se wrote:
On Sat, May 22, 2010 at 09:15, cyril romain cyril.rom...@gmail.com wrote:
On Mon, Nov 30, 2009 at 10:42 AM, Nikolai Weibull n...@bitwi.se wrote:
On Sun, Nov 29, 2009 at 09:55, cyril romain cyril.rom...@gmail.com
wrote:
Here
On Tue, May 25, 2010 at 12:48, Christian Brabandt cbli...@256bit.org wrote:
On Mon, May 24, 2010 10:06 pm, Bram Moolenaar wrote:
I also changed it to put the undofile with the edited file. That should
work, as writing a file usually means the undofile can be written there
as well. It's
2010/5/25 Dominique Pellé dominique.pe...@gmail.com:
Nikolai Weibull wrote:
That said, I think persistent undo is more or less useless and, well,
just a big pile of potential problems. Persistent undo is in the
version control system, not in the editor.
I think this is a bit harsh.
And I
On Tue, May 25, 2010 at 19:42, Christian Brabandt cbli...@256bit.org wrote:
On Di, 25 Mai 2010, Nikolai Weibull wrote:
2010/5/25 Dominique Pellé dominique.pe...@gmail.com:
Nikolai Weibull wrote:
That said, I think persistent undo is more or less useless and, well,
just a big pile
On Tue, May 25, 2010 at 21:04, Christian J. Robinson hept...@gmail.com wrote:
On Tue, 25 May 2010, Nikolai Weibull wrote:
And no one forced you to defend this feature.
True, nobody is forcing anybody to defend the feature, but what do you
expect to happen when you complain about it?
I
On Tue, May 25, 2010 at 22:38, Jordan Lewis jordanthele...@gmail.com wrote:
For example, pretend you're developing the ultimate novel Vim feature, but
you've caused a bug, and want to trace it in gdb. You edit Vim's makefile to
enable -g in CFLAGS, recompile, track down the bug, and want to
On Mon, Dec 28, 2009 at 21:26, James Vega james...@jamessan.com wrote:
On Mon, Dec 28, 2009 at 05:24:33PM +0100, Bram Moolenaar wrote:
Dennis Benzinger wrote:
That's a nice Christmas present :-)
Will the repository be hosted on code.google.com or do you plan to setup
Mercurial on
On Mon, Jan 4, 2010 at 22:54, Nikolai Weibull n...@bitwi.se wrote:
On Mon, Jan 4, 2010 at 22:41, Ernie Rael e...@raelity.com wrote:
On 1/4/2010 12:16 PM, Nikolai Weibull wrote:
Do either support tracking branches and similar stuff in a simple way?
http://mercurial.selenic.com/wiki
On Sun, Nov 29, 2009 at 09:55, cyril romain cyril.rom...@gmail.com wrote:
Here is a patch for yaml syntax highlighting.
I’ll review it.
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
With
set backupcopy=auto
Vim on Cygwin 1.7 removes write permission when writing a file not
owned by the current user on a Samba share. I realize that this can
be a Cygwin (1.7) problem, so I’m mainly asking whether anyone else
has stumbled upon this problem. The Samba share has ACL support
On Wed, Sep 23, 2009 at 17:32, Matt Wozniski m...@drexel.edu wrote:
On Wed, Sep 23, 2009 at 11:02 AM, Nikolai Weibull wrote:
Vim on Cygwin 1.7 removes write permission when writing a file not
owned by the current user on a Samba share. I realize that this can
be a Cygwin (1.7) problem, so
On Fri, Jul 17, 2009 at 19:48, mobi philm...@mobiphil.com wrote:
Can you please do something about your line wrapping? Trying to read
your messages is getting rather annoying.
if you are reffering to me I do my best with manual wrapping, I can use for
the moment only the web browser to
On Fri, Jul 17, 2009 at 19:50, mobi philm...@mobiphil.com wrote:
Considering that you seem to have posted your first message to this
list about one week ago, yes, that seems about right.
sorry, but do not understand your comment
Precisely my point.
On Fri, Jul 17, 2009 at 01:00, StarWingweasley...@sina.com wrote:
On 7月17日, 上午5时17分, Nikolai Weibull n...@bitwi.se wrote:
Now you’re losing me again. What does this matter? Copy-on-write?
It seems that you’ve just read a book on operating-system design or
something and want to, ahem
On Fri, Jul 17, 2009 at 11:49, StarWingweasley...@sina.com wrote:
On 7月17日, 下午4时39分, Nikolai Weibull n...@bitwi.se wrote:
On Fri, Jul 17, 2009 at 01:00, StarWingweasley...@sina.com wrote:
IMHO, Vim has several issues:
- it has separate Eval system and Inner implement. so you can't
On Thu, Jul 16, 2009 at 03:41, StarWingweasley...@sina.com wrote:
Of course I am not pretending to add a c++ compiler for the highlighting.
That would be against the basic principle vim is the fastest editor. Any
feature
no, IMHO vim is not the fastest editor. you can try use Vim open a 2GB
On Thu, Jul 16, 2009 at 00:05, Tony
Mechelynckantoine.mechely...@gmail.com wrote:
On 15/07/09 14:43, mobi phil wrote:
Look, I think I am enough mature and have years of IT, I know how to
attack a problem.
Considering that you seem to have posted your first message to this
list about one
On Tue, Feb 24, 2009 at 05:37, Bram Moolenaar b...@moolenaar.net wrote:
Markus Heidelberg wrote:
Nikolai Weibull, 23.02.2009:
On Sun, Feb 22, 2009 at 23:16, Bram Moolenaar b...@moolenaar.net wrote:
Markus Heidelberg wrote:
Bram, can you include this? I got no response from
On Fri, Feb 20, 2009 at 10:16, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 20/02/09 05:45, Bram Moolenaar wrote:
Changing this behavior will not be easy, so you will have to come up
with some kind of proof that the current mechanism may fail.
Also, what about the case when a
On Sun, Jan 4, 2009 at 16:26, Adam Osuchowski ad...@zonk.pl wrote:
Nikolai Weibull wrote:
I haven't really understood what the problem is (I don't believe that
there actually is one),
There is a non-zero time period between open file and write complete
content. Because vim truncate file
On Sun, Jan 4, 2009 at 23:19, Charles E. Campbell, Jr.
drc...@campbellfamily.biz wrote:
Nikolai Weibull wrote:
No, I mean both O_EXCL (so that a file hasn't been created in between
the time the original file has been renamed and the new one opened - a
case so far not mentioned
On Wed, Oct 22, 2008 at 13:19, Doug Kearns [EMAIL PROTECTED] wrote:
On 10/21/08, Nikolai Weibull [EMAIL PROTECTED] wrote:
Has remove() always thrown an error if idx is beyond the end of list?
Either way, what's the reasoning behind it doing so? If the items
aren't there to begin
On Wed, Oct 22, 2008 at 16:25, James Vega [EMAIL PROTECTED] wrote:
On Wed, Oct 22, 2008 at 03:54:23PM +0200, Nikolai Weibull wrote:
If I say remove(list, 8, -1) I expect it
to give me a list of the first 8 elements in list.
This is odd since, as pointed out earlier, Bram modelled the List
On Wed, Oct 22, 2008 at 17:06, Tony Mechelynck
[EMAIL PROTECTED] wrote:
It has everything to do with syntax.
What you're talking about is semantics. There's a difference.
The documented syntax (at :help remove()) says if {end} is before {idx}
it's an error.
(Blurb condensed to the fact
Has remove() always thrown an error if idx is beyond the end of list?
Either way, what's the reasoning behind it doing so? If the items
aren't there to begin with, then great, that's precisely what I want.
The documentation should be updated to reflect this state of affairs.
Here's a patch:
On Tue, Oct 21, 2008 at 22:29, Tony Mechelynck
[EMAIL PROTECTED] wrote:
On 21/10/08 13:53, Nikolai Weibull wrote:
Has remove() always thrown an error if idx is beyond the end of list?
Either way, what's the reasoning behind it doing so? If the items
aren't there to begin with, then great
On Mon, Jul 21, 2008 at 02:02, Michael Schaap [EMAIL PROTECTED] wrote:
It looks like syntax/yaml.vim is rather broken in vim 7.2b. For a start,
every single lower case 't' is marked as an error.
This is obviously caused by a missing '\'. That specific one is easy enough
to fix, but at a
On Mon, Jul 21, 2008 at 12:01, Michael Schaap [EMAIL PROTECTED] wrote:
On 21-Jul-2008 10:28, Nikolai Weibull wrote:
I'm really sorry syntax/yaml.vim has been so bugged. I was hoping to
be able to rewrite it to fully parse yaml code, but I haven't had
time.
Thanks for the quick response
On Sun, Jul 20, 2008 at 16:01, Bram Moolenaar [EMAIL PROTECTED] wrote:
Jan Minar wrote:
The configure can just use a fixed file name in the current directory.
Anyway, I have adapted some code from src/auto/configure that will
work on systems without mktemp(1) -- patch attached.
There
OK, so it turns out, after having to go to the source, that the
'include' pattern only gets fed one line at a time. For the DTD
filetype, having multiple lines would be nice, as that would allow you
to do the following:
setlocal
On Fri, Jul 18, 2008 at 00:54, Jan Minář [EMAIL PROTECTED] wrote:
The attacker has to create the temporary file
``/tmp/Makefile-confPID'' before it is first written to at (1). In
the time between (1) and (2), arbitrary commands can be written to the
file. They will be executed at (2).
On Fri, Jul 18, 2008 at 11:46, Bram Moolenaar [EMAIL PROTECTED] wrote:
Unfortunately the patch breaks configure for me:
86: checking Python's configuration directory...
/usr/local/lib/python2.5/config
87: usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
88:
On Thu, Jul 17, 2008 at 12:30, Richard Hartmann
[EMAIL PROTECTED] wrote:
Syntax elements are detected highlighted in the wrong places.
Two examples I have known for some time but never got around to
do much about them are:
Posting sooner rather than later is always better. That almost
2008/7/17 James Vega [EMAIL PROTECTED]:
I'll jump in here and post a problem I've been meaning to contact you
about, as well.
somecommand $somevar
othercommand
Zsh's here-string is triggering the here-doc syntax highlighting and
therefore causes all of the remaining script to be
On Tue, Jul 8, 2008 at 19:03, Tony Mechelynck
[EMAIL PROTECTED] wrote:
On 08/07/08 17:27, Nikolai Weibull wrote:
On Tue, Jul 8, 2008 at 16:57, ThoML[EMAIL PROTECTED] wrote:
Have you tried contacting Nikolai Weibull, the maintainer-of-record?
Yes, maintainer ... uhm ... not yet.
I read
On Tue, Jul 8, 2008 at 16:57, ThoML [EMAIL PROTECTED] wrote:
Have you tried contacting Nikolai Weibull, the maintainer-of-record?
Yes, maintainer ... uhm ... not yet.
I read the mailing list. It's actually better to write to vim_dev, as
more eyes will see it there. I can't promise
On Wed, May 28, 2008 at 1:37 AM, Antony Scriven [EMAIL PROTECTED] wrote:
Hi all. I've often encountered the situation where a plugin
maps keys that I've wistfully mapped in my vimrc. I think it
would be useful for a user to be able to prevent this, say
by using a notation such as
:map
On Sun, May 18, 2008 at 8:44 PM, Tony Mechelynck
[EMAIL PROTECTED] wrote:
Note, that you probably do not want to use BOM with UTF-8.
See http://unicode.org/faq/utf_bom.html#29 (Q: Can a UTF-8 data stream
contain the BOM character (in UTF-8 form)? If yes, then can I still
assume the remaining
On Tue, May 20, 2008 at 12:47 PM, Tony Mechelynck
[EMAIL PROTECTED] wrote:
On 20/05/08 09:11, Nikolai Weibull wrote:
On Sun, May 18, 2008 at 8:44 PM, Tony Mechelynck
[EMAIL PROTECTED] wrote:
Note, that you probably do not want to use BOM with UTF-8.
See http://unicode.org/faq/utf_bom.html
'langmap' interacts with :nmap and that's fine. However, it also
interacts with :nmap when the rhs is a Plug or SID mapping.
That's not fine. Am I missing something, or is this a bug?
Here's a test:
nmap t SIDbug
nnoremap SIDbug Esc:echoerr actually, i'm not a bug if this is
echoed as an
On Thu, Apr 17, 2008 at 12:25 AM, Paul LeoNerd Evans
[EMAIL PROTECTED] wrote:
It's also future-proof. If, in 10 years time when we all have
pressure-sensitive keys, I type enter or ENTER by hitting the keys
harder, and xterm sends
By which time we'll all have flying cars.
2008/4/8 Mikolaj Machowski [EMAIL PROTECTED]:
Dnia Tuesday 08 of April 2008, Bram Moolenaar napisał:
I have been preparing a talk for the upcoming FISL conference in Brazil:
http://fisl.softwarelivre.org/9.0/www/
One of the items I planned to discuss is why Vim has no floating point
On Sat, Mar 29, 2008 at 8:14 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Considering the recent OOXML fuzz I have lowered my appreciation for
standards considerably.
Considering that much of what people are complaining about regarding
OOXML is things that exist in OOXML due to Office's
On Thu, Mar 27, 2008 at 1:16 PM, Antony Scriven [EMAIL PROTECTED] wrote:
On 27/03/2008, Ben Schmidt [EMAIL PROTECTED] wrote:
Antony Scriven wrote:
I'd prefer the longest match rather than the
first alternative (as specified by POSIX)
An interesting twist. Can you clarify which
On Thu, Mar 27, 2008 at 5:37 PM, Antony Scriven [EMAIL PROTECTED] wrote:
On 27/03/2008, Nikolai Weibull [EMAIL PROTECTED] wrote:
/left-most/ longest. Big difference.
I thought the `left-most' part was a given and we were
discussing which of the alternatives would be subsequently
On Jan 8, 2008 6:45 PM, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
It might help folks help you if you included the
get_command_mode_range() function.
Ugh, yeah, I'm beginning to have a suspicion as to what the problem is:
function! s:get_command_mode_range(type)
let b = line('[)
let
On Dec 4, 2007 5:40 PM, Tony Mechelynck [EMAIL PROTECTED] wrote:
skelker wrote:
I have noticed that swap file writes are done in 4K blocks, but file
reads are done in 64K blocks. If it isn't possible to adjust this
behavior with configuration, then I suggest opening this up as a
On Dec 4, 2007 7:40 PM, Tony Mechelynck [EMAIL PROTECTED] wrote:
Regardless, I wonder how much of an issue this really is. It seems to
me that the code is quite optimized
How much of an issue the size of the writes, that is.
[1] fsync is a slow operation, especially on a reiser4
On Nov 20, 2007 5:53 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
When at the end of a buffer, daw on one space won't delete anything.
Not that I think this is expected behavior, but this might be
intentional (that is, failing to select any word after the cursor
On Nov 20, 2007 8:57 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
When at the end of a buffer, daw on one space won't delete anything.
Not that I think this is expected behavior, but this might be
intentional (that is, failing to select any word after
On Nov 11, 2007 1:24 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Matthew Wozniski wrote:
Now that 88 and 256 color terminals are so ubiquitous, I find it
frustrating that very few colorschemes support 256 color terminals.
Unfortunately, writing a colorscheme that properly supports
echo glob('~/{,}')
/home/user//
/home/user//
The bug is that an extra slash is added at the end. It's only a
minory issue, as slashes are usually folded by the OS anyway, but it
would be better if they weren't added.
Another issue is that there's doesn't seem to be a way to escape a
comma
On Nov 12, 2007 3:09 PM, Vladimir Marek [EMAIL PROTECTED] wrote:
Another issue is that there's doesn't seem to be a way to escape a
comma inside a brace expansion. Neither two commas in a row or a
backslash seem to generate a comma.
glob behaves depending on your shell settings. Out of
On Nov 12, 2007 3:36 PM, Vladimir Marek [EMAIL PROTECTED] wrote:
Another issue is that there's doesn't seem to be a way to escape a
comma inside a brace expansion. Neither two commas in a row or a
backslash seem to generate a comma.
glob behaves depending on your shell settings.
On Nov 12, 2007 3:40 PM, Matt Wozniski [EMAIL PROTECTED] wrote:
On Nov 12, 2007 9:16 AM, Nikolai Weibull [EMAIL PROTECTED] wrote:
On Nov 12, 2007 3:09 PM, Vladimir Marek [EMAIL PROTECTED] wrote:
Another issue is that there's doesn't seem to be a way to escape a
comma inside
On Nov 12, 2007 8:42 PM, Gautam Iyer [EMAIL PROTECTED] wrote:
Finally, t_Co is a bad measure. If you're not running xterm, t_Co is
read directly from your termcap / terminfo files. The default terminfo
files shipped with most distributions sets it to 8 colors. The user has
to tweak a little
Ctrl-X Ctrl-F does filename completion rooted at the current working
directory. I would think that one probably wants to complete
filenames rooted at the current buffer's location. Is this something
for the TODO perhaps?
--~--~-~--~~~---~--~~
You received this
On 10/29/07, Ben Schmidt [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
Ctrl-X Ctrl-F does filename completion rooted at the current working
directory. I would think that one probably wants to complete
filenames rooted at the current buffer's location. Is this something
for the TODO
On 10/23/07, Andy Wokula [EMAIL PROTECTED] wrote:
Richard Hartmann schrieb:
On 23/10/2007, Andy Wokula [EMAIL PROTECTED] wrote:
:syn region zshSubst matchgroup=zshSubstDelim start='\${' skip='\\}'
\ end='}' [EMAIL PROTECTED],zshBrackets,zshQuoted,zshString
This fixes the
On 10/22/07, Tony Mechelynck [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
How difficult would it be to implement a console server using sockets?
if_xsrvcmd.c looks quite complicated, but I get the felling that a
simple socket interface wouldn't require quite as much code.
Anyone
On 9/26/07, Gregory Seidman [EMAIL PROTECTED] wrote:
Does anyone have any suggestions? Here's the output of gvim --version:
#if defined(UNIX) !defined(__BEOS__) !defined(MACOS_X)
# define MAY_FORK
int dofork = TRUE;
#endif
So no, it seems you simply can't fork under MACOS_X. I
Could :catch be allowed to take a variable containing a pattern
instead of only literal patterns? I have the following function
Turn the error-number NUMBER into a pattern that can be used in a :catch
expression to match that error when generated by Vim.
function now#vim#error(number)
On 9/19/07, Charles E Campbell Jr [EMAIL PROTECTED] wrote:
Larson, David wrote:
Believe me, I have isolated the problem down to that one line. You
probably can't reproduce the problem because you are using a different
build than I am (GTK2).
You know, black lettering on a dark blue
On 9/16/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
[Request to allow referencing namespace#variable inside functions
without g: prefix]
I don't see a good reason to make an exception. Requiring the use of g:
or s: makes it consistent. Otherwise there would
On 9/17/07, Tony Mechelynck [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
Ranting aside, the prefix of number above is now#. I mean, have I
gone to the trouble to declare what namespace the variable is in,
shouldn't that be enough? And
let s:bug#number = 1
results
On 9/17/07, Tony Mechelynck [EMAIL PROTECTED] wrote:
Please cut out parts that aren't relevant to what you're replying to.
Nikolai Weibull wrote:
What is lambda supposed to mean here?
Hm? What is the exact English equivalent? random, average, any, John Q.
Public, typical, ordinary
Create autoload/bug.vim:
let s:cpo_save = cpo
set cpovim
function bug#reproduce()
echo bug#number
endfunction
let bug#number = 1
let s:cpo_save = cpo
set cpovim
Start vim and run
:call bug#reproduce()
which will give you the following output (instead of 1):
Error detected while
On 9/16/07, Nikolai Weibull [EMAIL PROTECTED] wrote:
function bug#reproduce()
echo bug#number
endfunction
let bug#number = 1
:call bug#reproduce()
which will give you the following output (instead of 1):
Error detected while processing function bug#new:
line1:
E121: Undefined
% vim
:new
:autocmd BufWinLeave buffer=1 :2wincmd w | quit
:wincmd p
:q
Guess what, buffer 1 is still loaded and displayed. Like, WTF?
The reason I want to do this is that I have opened a window that I
want to be dependent on the first window being visible. This is for
doing diffs.I've
I have the following function and binding:
noremap silent g: Esc:set operatorfunc=SIDget_command_mode_rangeCRg@
function! s:get_command_mode_range(type)
let b = line('[)
let e = line('])
if b e
let range = '.,+' . (e - b)
elseif b == e
let range = '.'
else
let range =
On 8/27/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
So it seems that there's something strange going on in what line is
being set for the ] mark when performing a search under these
conditions, coupled with patterns that match at the very beginning of
a line
97 matches
Mail list logo
