On 10/29/07, Dominique Pelle [EMAIL PROTECTED] wrote:
I have the following line in my .vimrc which does exactly what
you're looking for, and I find it very useful:
autocmd BufEnter * exe 'cd ' . substitute(expand(%:p:h), , , g)
You might prefer this line:
au BufEnter * if ft != 'help' |
On Nov 12, 2007 4:29 AM, Gautam Iyer [EMAIL PROTECTED] wrote:
On Mon, Nov 12, 2007 at 02:56:24AM -0500, Matthew Wozniski wrote:
Do all the terminals supporting 88 and 256 colors really use the same
color values?
Well... As far as I can tell, they seem to _default_ to the same
On Nov 12, 2007 9:42 AM, Nikolai Weibull [EMAIL PROTECTED] wrote:
Either way, there's no way to escape a comma inside braces.
:echo glob('/tmp/{a,b\\054c}')
That works for shell=/bin/zsh and shell=/bin/tcsh for me, though not
for shell=/bin/bash. While I agree that you ought to be able to
On Nov 12, 2007 9:56 AM, Vladimir Marek [EMAIL PROTECTED] wrote:
Personally I would like to see something like glob_internal() which
would do globbing entirely in c without accessing your shell. But I'm
not going to write the patch, so I just silently hope :) Or having
readdir to be able to
On Nov 17, 2007 6:03 AM, Narayanan A R [EMAIL PROTECTED] wrote:
I use to type :e folder path for opening a folder in VIM running
on Windows and it used to work. However the same doesn't work any more
for Linux. It opens only files. I am using Ubuntu 7.10.
This feature is really helpful to
On Dec 3, 2007 2:05 PM, Charles E. Campbell, Jr. wrote:
Matt Wozniski wrote:
Fixing that to use a script-local variable would definitely be
a worthwhile change that should be made ASAP, though it still wouldn't
protect you from plaintext passwords being in your core files.
Yes, I've done
On Dec 3, 2007 4:59 PM, Charles E. Campbell, Jr. wrote:
Matt Wozniski wrote:
On Dec 3, 2007 2:05 PM, Charles E. Campbell, Jr. wrote:
Assuming that I have an encrypt/decrypt function pair, the pid could be
used as a single-session p/w that would be transparent to the user. I
don't see
On Dec 5, 2007 1:21 AM, thomas wrote:
Thank you, Ben! That's exactly what I meant.
For this, keeping a variable in a script-local function would suffice
-- I personally haven't found a way yet to access a s:var.
...
Also, you will most likely have to define functions that decrypt the
On Nov 12, 2007 5:41 AM, Matt Wozniski [EMAIL PROTECTED] wrote:
So, I would certainly welcome some advice on how querying
can be done reasonably...
Gnome-terminal and Konsole, at least, do not seem to be able
to report back their colors... So, I guess one (pseudocode)
approach
On Dec 21, 2007 5:18 AM, Nico Weber [EMAIL PROTECTED] wrote:
2) There is no algorithm available to programmatically judge the
perceived differences between colors that suits our purposes. We do
well with CIE L*a*b*, but not better than the stepping algorithm I
proposed first, and in
On Dec 20, 2007 11:44 PM, Matt Wozniski [EMAIL PROTECTED] wrote:
...
So, I've reworked the patch to support, in addition to the
xterm-compatible palette, Eterm and Konsole's palettes. Which palette
is used for the matching is controlled by a new option, 'termpalette'
(short name 'tpal
On Jan 6, 2008 9:09 AM, Bram Moolenaar wrote:
We haven't been using printf so far, thus this needs to be tested to
find any system where it doesn't work. The opengroup isn't always
right (I don't think they cover Cygwin).
The cygwin developers regularly reference opengroup man pages on the
On Jan 10, 2008 2:39 PM, James Vega [EMAIL PROTECTED] wrote:
On Thu, Jan 10, 2008 at 08:28:14PM +0100, Tony Mechelynck wrote:
The parentheses should have been percent-escaped, i.e., replaced by a
percent
sign and their hex value (00-FF) as in
http://www.vim.org/%28test%29
On Jan 23, 2008 11:15 AM, Erik Falor wrote:
On 23/01/2008, Dasn wrote:
I don't think #!/usr/bin/env vim -S is workable on all platforms.
$ cat test.vim
#!/usr/bin/env vim -S
echo this is a Vim script
quit
$ chmod +x test.vim
$ ./test.vim
env: vim -S: No such file or directory
On Feb 4, 2008 9:18 AM, krischik wrote:
On the other hand use of extended attributes could solve a problem
with 5 lines of code where solving the same problem without could cost
you 50. Determine file types, text file line endings and text file
encoding come to my mind here. Ask Bram how
On Feb 4, 2008 4:29 PM, krischik wrote:
On 4 Feb., 21:10, Matt Wozniski wrote:
While this would be nice, it would require support code from every
application you have. It may only be 6 lines, but 6 lines * 5000
binaries is much more code than is in vim for line ending detection
On Mon, Feb 4, 2008 at 4:55 PM, [EMAIL PROTECTED] wrote:
On Jan 12, 1:57 pm, Matt Wozniski wrote:
On Jan 12, 2008 12:49 PM, Ben Schmidt wrote:
noremap Space PageDown
noremap S-Space PageUp
However, in Linux, running vim inside the gnome-terminal 2.18.2 (or
when
On Sun, Feb 24, 2008 at 7:13 PM, Tony Mechelynckwrote:
Matt Wozniski wrote:
If anyone remembers this thread, the OP complained that he could
neither get s-space to be recognized independently of space in vim
nor in a GTK2 or Gnome2 gvim. I gave him a solution to get it to work
On Mon, Feb 25, 2008 at 9:27 AM, Andrew McCarthy wrote:
On Mon, Feb 25, 2008 at 07:57:02AM -0500, James Vega wrote:
On Mon, Feb 25, 2008 at 12:06:24PM +, Andrew McCarthy wrote:
Thoughts? Any better/cleaner ideas?
mkdir -p ~/.vim/tmp
echo 'set directory=$HOME/.vim/tmp'
Sent this to Bram instead of the list accidentally; forwarding.
-- Forwarded message --
From: Matt Wozniski [EMAIL PROTECTED]
Date: Mon, Feb 25, 2008 at 4:02 PM
Subject: Re: Mapping s-space with GTK2 (was write 'set t_Co=256',
scroll and keybind problems)
To: Bram Moolenaar
On Thu, Mar 27, 2008 at 2:47 PM, Bram Moolenaar wrote:
Xiaozhou Liu wrote:
During the development of the new regexp, one thing confuses me a lot:
ordered alternation. (e.g. given r.e. 'ab\|abc' and text 'abc', 'ab'
matched, not 'abc')
I know that 100% compatibility is one of the
On Tue, Jun 24, 2008 at 2:48 AM, Thibault Taillandier wrote:
How to reproduce the bug :
- start vim (with an existing file or a new file)
- type in this command:
:vs ~ap
- And press tab for auto-completion.
- vim crashes with this message (my vim is in french):
Vim: Signal mortel ABRT
On Wed, Aug 20, 2008 at 4:33 AM, Tony Mechelynck wrote:
On 20/08/08 09:47, Jan Minář wrote:
The above will of course not work. The following will:
/* We use an obscure glibc function -- check out the man page! */
clockface =(xclock)pwnme (a, b, x + y);
/*
On Thu, Aug 21, 2008 at 12:55 AM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Matt Wozniski wrote:
Jan got the exploit right, but formatted his modeline wrong. Try this
document:
/* We use an obscure glibc function -- check out the man page! */
clockface = (xclock)pwnme (a, b, x + y
On Thu, Aug 21, 2008 at 1:56 AM, Ben Schmidt wrote:
place your cursor on 'pwnme', and press K. xclock appears.
Yeah, this is the kind of exploit where you have to tell the user to do
something stupid and them blame Vim that the user is stupid.
Yes. Still...that seems to be the current
On Thu, Aug 21, 2008 at 1:05 PM, Tony Mechelynck wrote:
On 21/08/08 08:25, Matt Wozniski wrote:
[...]
In that vein, perhaps using the shell should be an option... but
doubtless the best default behavior is to use system(3) for places
like :! where shell expansion is good,and execlp
Not sure what's going on here, but I've found a crash that's easy to
reproduce. First, open two X11 enabled vim (not gvim) processes. In
the first, do:
:let @+ = repeat('a', 1024*1024)
in order to store 1MB of data to the clipboard. The exact amount is
irrelevant, but the larger the size, the
On Fri, Aug 15, 2008 at 2:02 AM, Matt Wozniski wrote:
synIDattr() currently does not support the ability to read a 'guisp'
attribute from a highlight group, even though the underlying C
function it exposes does support it. I've attached a patch to update
the interface and docs to allow
On Fri, Aug 22, 2008 at 6:41 PM, Tony Mechelynck wrote:
On 22/08/08 21:20, Jan Minář wrote:
Thanks. I'll have a good look at it later. One thing I noticed: you
don't need to give an error message for running out of memory at this
level, it's already done at a lower level in alloc(). There
On Sun, Aug 24, 2008 at 11:22 AM, Robert Webb wrote:
Hi,
The help for sort() says the following with respect to the function
reference argument:
...The function is invoked with two
items as argument and must return zero if they are equal, 1 if
the first one sorts after the
On Fri, Aug 15, 2008 at 2:02 AM, Matt Wozniski wrote:
synIDattr() currently does not support the ability to read a 'guisp'
attribute from a highlight group, even though the underlying C
function it exposes does support it. I've attached a patch to update
the interface and docs to allow
On Tue, Sep 2, 2008 at 6:42 AM, Tony Mechelynck wrote:
I'm seeing your message and I don't know the answer. Do you want a
similar message from everyone who doesn't know the answer?
Naturally not; your response was far more wasteful than my post
already, and not just because of wasting twice
On Thu, Sep 4, 2008 at 4:09 PM, Bram Moolenaar wrote:
Tyler Spivey wrote:
hello. I have noticed that starting from 7.1.329, using vim in the
console with the encoding set
to utf8, there is a bug with redrawing characters.
The characters show up on the screen fine (at least to my screen
Using ==, strings and numbers can compare as equal, and using index()
on a list, this is not the case:
:echo 2 == 2 Returns 1
:echo index( [ 2 ], 2) Returns -1
The docs just say that index() will Return the lowest index in |List|
{list} where the item has a value equal to {expr},
These two functions ought to behave identically, but don't... For some
reason, the :catch never gets triggered for the Broken one.
function! Working()
try
let y = x
return y
catch /^Vim\%((\a\+)\)\=:E121/
Handle 'Undefined variable' errors
return 42
endtry
endfunction
On Sun, Sep 28, 2008 at 4:35 PM, Tony Mechelynck wrote:
On Sun, Sep 28, 2008 at 9:40 AM, John Hughes wrote:
I am trying to write a command that substitutes some Ascii characters
with a Unicode character. The following substitution works when
entered directly:
:%s/\.\.\./…/eg
However, when
On Mon, Oct 13, 2008 at 8:37 PM, John Little wrote:
On Oct 14, 12:13 pm, frankjas wrote:
I have been encountering an intermittent coredump ...
I rebuilt vim from source with symbols after I stumbled on a
reproduceable test case today...
Brilliant.
follows. It looks like the field
On Tue, Oct 21, 2008 at 4:29 PM, Tony Mechelynck wrote:
On 21/10/08 13:53, Nikolai Weibull wrote:
Here's a patch:
Please apply your patches to the latest version of the file. In eval.txt
dated 2008 Sep 14, line, 4482 to 4489 are
...
within the help for remote_send(); IOW your pointer is 14
On Sat, Nov 8, 2008 at 11:18 PM, Tony Mechelynck wrote:
Configure is supposed to check whether one of the system provided
string-move operations handle overlap. Here's what I see in the logs and
files produced by configure on my system:
snip
So I suppose mch_memmove should be used
On Mon, Nov 17, 2008 at 6:02 PM, Dominique Pelle wrote:
2008/11/17 Dominique Pelle:
Hi
I observe a bug with the latest Vim-7.2.42 (huge) on Linux x86.
It's not recently introduced since I can reproduce at least with
Vim-7.1.314 which comes with Ubuntu-8.10. It only happens in
a terminal
On Tue, Dec 9, 2008 at 3:40 AM, Patrick Texier wrote:
Attached patch disallows 'encoding' in a modeline but not in secure
mode.
Looks like a good idea to me, especially since the vim help explicitly
says that 'encoding' should either be set in ~/.vimrc or not at all...
In fact, I think it
At :help :set-termcap, an example shows the command
:set M-b=^[b
This command does not work as expected when 'encoding' is set to
something multibyte. The reason seems to be that vim recognizes the
input bytes 0x1B 0x62 as a metafied 'b', and then stuffs 0xE2 into its
internal text buffers - a
For the life of me, I can't seem to get vim to recognize, eg, xHome
and Home as separate keycodes. For instance...
vim -u NONE -N
:set Home? xHome?
t_kh Home ^[[1~
t_kh Home ^[[1~
:set Home=
:set xHome?
E518: Unknown option: xHome?
Is this intentional behavior? What's the point of
John Beckett wrote:
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize,
eg, xHome and Home as separate keycodes.
Perhaps the following is an explanation:
:help version7
/xHome
Previously Home and xHome could be mapped separately.
This had the disadvantage
Bram Moolenaar wrote:
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize, eg, xHome
and Home as separate keycodes. For instance...
That's a bug. This patch should fix it:
Yes, that seems to fix it for me, xterm on Linux.
~Matt
function! ReturnArgs(...)
return a:000
endfunction
Seems to work fine?
echo ReturnArgs(1, 2, 3)
SEGV
echo string(ReturnArgs(1, 2, 3))
function! MakeArgsDict(...)
return { 'args': a:000 }
endfunction
E685 Internal Error
echo MakeArgsDict(1, 2, 3)
SEGV
echo string(MakeArgsDict(1, 2,
On Mon, Dec 15, 2008 at 2:42 PM, Dominique Pelle wrote:
Matt Wozniski wrote:
function! ReturnArgs(...)
return a:000
endfunction
function! MakeArgsDict(...)
return { 'args': a:000 }
endfunction
I can reproduce that with vim-7.2.69 on Linux.
Following patch seems to fix it, but I'm
On Mon, Dec 15, 2008 at 4:49 PM, Matt Wozniski wrote:
On Mon, Dec 15, 2008 at 2:42 PM, Dominique Pelle wrote:
Matt Wozniski wrote:
function! ReturnArgs(...)
return a:000
endfunction
function! MakeArgsDict(...)
return { 'args': a:000 }
endfunction
I can reproduce that with vim
On Thu, Dec 18, 2008 at 8:01 AM, Markus Heidelberg wrote:
When typing ^Vu and the codes above in terminal Vim, I always get these
squares, i.e. the characters cannot be displayed, in vim -g it works. Is
this a font issue?
Yes; your font just must be missing those glyphs.
Also, Konqueror
On Fri, Dec 26, 2008 at 6:49 AM, Florian Rehnisch wrote:
Hi folks,
it is said, that translators are the best profreaders.
;-)
Sometimes, I make annotations. Let's see what I have:
# type: Plain
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce this are
complicated, and possibly very specific to the version of the runtime
files and such
On Sat, Dec 27, 2008 at 3:15 AM, Dominique Pelle wrote:
2008/12/27 Matt Wozniski wrote:
I found a SEGV that I can reproduce reliably, but can't seem to track
down. It SEGVs without gdb or valgrind, doesn't SEGV under valgrind,
and SEGVs under gdb. The steps that I'm using to reproduce
On Tue, Dec 30, 2008 at 1:14 PM, Daniel Schierbeck wrote:
I have added several directories to my runtimepath, each corresponding
to a git repository. For example, I have a directory ~/Projects/vim-
rack that contains ftdetect/rack.vim and syntax/rack.vim. I'm able to
manually :set
On Wed, Dec 31, 2008 at 8:11 AM, Tony Mechelynck wrote:
On 31/12/08 07:48, Matt Wozniski wrote:
On Tue, Dec 30, 2008 at 1:14 PM, Daniel Schierbeck wrote:
I hope there's a simple workaround.
Sorry I couldn't come up with the solution earlier on IRC, but after
some sleep, I think I see
On Sat, Jan 3, 2009 at 11:27 PM, Adam Osuchowski wrote:
Cases like mbox files are not so rare. There are many examples of
simultaneously access to single file, but problem exists even without
concurrent modification.
A simple example: editing config file for some daemon. When vim
truncates
On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote:
On 06/01/09 12:31, anhnmncb wrote:
Hi, list, as title, if so, why can't many functions
still handle correctly with unicode? For example the func:
getline('.')[col('.')-1]
Can't return a charactor outside the range of ascii.
On 1/6/09, Tony Mechelynck wrote:
On 07/01/09 00:39, Matt Wozniski wrote:
On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote:
On 06/01/09 12:31, anhnmncb wrote:
Hi, list, as title, if so, why can't many functions
still handle correctly with unicode? For example the func
On 1/6/09, Tony Mechelynck wrote:
On 1/6/09, Matt Wozniski wrote:
echo matchstr(getline('.'), '\%' . col('.') . 'c.')
Again, col('.') is a byte index, not a column. What about virtcol('.')
instead?
Nope. \%15c is also a byte index, not a column (which is also
counter-intuitive, and brings
:help 'path' says
- When using |netrw.vim| URLs can be used. For example, adding
http://www.vim.org; will make :find index.html work.
This, however, does not actually work (and hasn't since vim 6.4.10, at
least). Attached patch fixes.
~Matt
Bram Moolenaar wrote:
Chris Littell wrote:
In the help file index.txt, the description for CTRL-W = should
mention that it also makes window widths equal. Right now it looks
like there is no command to do this until you see the detailed
description.
I'll make it: make all
Please bottom post on this list... I'm reformatting...
On Wed, Jul 21, 2010 at 6:05 AM, mikeyao yaoweiz...@gmail.com wrote:
On Jul 21, 5:38 pm, Bram Moolenaar b...@moolenaar.net wrote:
Mikeyao (?) wrote:
Why not javascript interface ?
The code has developed.
On Wed, Jul 21, 2010 at 10:11 AM, duffman wrote:
Hi,
I tried to look up information online on this but wasn't able to find
anything that worked. I used Vi at my old job and loved the editing
features it provided. I've moved to a new place now and I am the only
developer here. I logged
On Wed, Jul 14, 2010 at 4:57 PM, Bram Moolenaar wrote:
Matt Wozniski wrote:
[about a patch to support #rrggbb in a terminal]
Where can I find the latest version of this patch? I only see one that
is two years old.
As Benjamin Haskell noted, I decided to shoot for a vimscript
On Fri, Jul 23, 2010 at 2:06 PM, Nikolai Weibull n...@bitwi.se wrote:
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
On Tue, Jul 27, 2010 at 9:17 AM, Dimitar DIMITROV wrote:
I tried with Vim 7.3b and the problem is gone when cursorline is on but I
still
find it strange that vertical bars and stars would appear when highlighting
the
text. It may be relevant for other filetypes but I don't think it is for
On Tue, Jul 27, 2010 at 12:12 PM, Matt Wozniski wrote:
On Tue, Jul 27, 2010 at 9:17 AM, Dimitar DIMITROV wrote:
I tried with Vim 7.3b and the problem is gone when cursorline is on but I
still
find it strange that vertical bars and stars would appear when highlighting
the
text. It may
To reproduce:
:echo repeat([{'a':'1'}], 2)
[{'a': '1'}, {...}]
expected output: [{'a': '1'}, {'a': '1'}]
:echo repeat([[0]], 2)
[[0], [...]]
expected output: [[0], [0]]
This seems to be caused by echo_string deciding that the data
structure is recursive, despite the fact that it definitely
On Wed, Jul 28, 2010 at 9:20 AM, Ingo Karkat sw...@ingo-karkat.de wrote:
Sorry, I haven't tried your patch yet, only reviewed it. I'd like to point out
the naming peculiarities for ftplugins (:help ftplugin-name), which I think
require additional filtering of the retrieved *.vim names:
| The
On Wed, Jul 28, 2010 at 9:24 PM, Benjamin Fritz fritzophre...@gmail.com wrote:
On Wed, Jul 28, 2010 at 3:39 PM, Bram Moolenaar b...@moolenaar.net wrote:
The documentation clearly says:
By default, HTML optimized for old browsers is generated. If you prefer
using
cascading style sheets
2010/8/14 Dominique Pellé dominique.pe...@gmail.com:
* I did set mouse=a. I can use the mouse to position the cursor
and mouse also works fine with Netrw (clicking on directories opens
them...). However, I cannot use the mouse to resize Vim's windows
(nothing happens when I click the
On Tue, Aug 17, 2010 at 5:26 PM, Bram Moolenaar wrote:
Björn Winckler wrote:
I for one would be very happy if the next version (vim74?) used this
scheme (i.e. where all new work happens on the default branch).
In my opinion the default branch should contain the stable version.
Most users
On Mon, Aug 23, 2010 at 4:45 PM, ZyX wrote:
Ответ на сообщение «Re: [BUG] Being provided some equal recursive structures,
equality operator never stops comparison»,
присланное в 17:34:55 23 августа 2010, Понедельник,
отправитель Adrien Axioplase Piérard:
But in vim, you cannot use assignment
2010/11/29 Bram Moolenaar b...@moolenaar.net:
Pádraig wrote:
Ensure vim is not recursively invoked (man-db does this)
when doing ctrl-[ on a man page reference
Shouldn't that be ctrl-] ?
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
On Sun, Feb 8, 2009 at 11:40 PM, Garrett Whelan whaled...@gmail.com wrote:
I would like to be able to access all the variables at a given time in Vim
without necessarily knowing what they are. Basically everything you would
see if you typed :let and :set. So in increasing order of difficulty
On Mon, Feb 9, 2009 at 5:56 PM, Andy Wokula wrote:
Here is another way to get the option names, it's basically
:set C-A
snip
The output is almost sorted and includes all and termcap as the
first two entries.
Wow. That is quite clever, I definitely wouldn't have thought of
that.
On Tue, Feb 10, 2009 at 4:35 PM, Charles Campbell wrote:
James Vega wrote:
I'm still curious what purpose vimballs serve over a standard archive
format like zip or tar.gz. From a distribution perspective, all they've
done is made my work harder when trying to include vim scripts in a
On Tue, Feb 10, 2009 at 9:48 PM, Charles E. Campbell, Jr. wrote:
Matt Wozniski wrote:
But let's not forget that they have significant disadvantages, too...
Vimballs made with new versions of the plugin don't work on older
vims.
There's been one problem with that -- 7.0 vimball doesn't
On Wed, Feb 11, 2009 at 11:06 AM, Tom Link micat...@gmail.com wrote:
Right. For the near term, supporting unzipping using a pure-vimscript
solution isn't terribly likely, but it's definitely possible OOTB in
vims built with +python, for example.
IMHO reliance on compiled-in +python support
On Wed, Feb 11, 2009 at 7:29 PM, Tony Mechelynck wrote:
On 11/02/09 16:23, Matt Wozniski wrote:
[...]
Well, of course I didn't mean that we should add the features to the
zip format. Rather, I meant we should do something more like XPI -
create a zip file, rename it to .vba, and let vim
On 2/17/09, Larson, DavidX S wrote:
Hello all,
I was working on my script when I ran across this unexpected behavior
with the if statement. The doc says:
:if {expr1} *:if* *:endif* *:en* *E171* *E579* *E580*
:en[dif]Execute the commands until the
On Tue, Feb 17, 2009 at 9:19 PM, Markus Heidelberg wrote:
Bram Moolenaar, 18.02.2009:
Markus Heidelberg wrote:
After reaching the end of the more prompt, hitting SPACE jumps out of
it. Add 'f' to avoid this problem and for consistency with 'b' in
scroll down a screen.
This also
src/fileio.c : vim_tempname() contains these lines:
if (GetTempFileName(szTempFile, buf4, 0, itmp) == 0)
return NULL;
/* GetTempFileName() will create the file, we don't want that */
(void)DeleteFile(itmp);
Is this really right? Is there any reason to call DeleteFile()
Motif and Athena recognize the 'ToolTip' highlight group, and will
change the fonts and colors of the balloons popped up over toolbar
entries. However, the colors aren't used for the balloons popped up as
a result of a balloonexpr.
This patch fixes that issue.
~Matt
diff --git
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
to run, as explained on my Windows HowTo
Hm. Support for using cygwin's gcc to do cross-compile
On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote:
On 08/03/09 02:35, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
On Sat, Mar 7, 2009 at 9:32 PM, Tony Mechelynck wrote:
On 08/03/09 03:15, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote:
using the -mno-cygwin option of the Cygwin gcc
compiler and the appropriate corresponding option of the linker.
This option will be removed
On Sat, Mar 7, 2009 at 10:29 PM, Tony Mechelynck wrote:
On 08/03/09 03:49, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 9:32 PM, Tony Mechelynck wrote:
[...]
The _option_ to compile native-Windows programs
using Cygwin gcc _is_ a useful thing, I can't imagine on what grounds
someone would
On Sat, Mar 7, 2009 at 9:21 PM, Steve Hall wrote:
On Sun, 2009-03-08 at 03:05 +0100, Tony Mechelynck wrote:
The only interest of Make_cyg.mak is to compile Vim binaries which
don't need Cygwin to run, using the -mno-cygwin option of the
Cygwin gcc compiler and the appropriate corresponding
On Sun, Mar 8, 2009 at 5:40 AM, Corinna Vinschen wrote:
On Mar 7 20:35, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
On Fri, Mar 13, 2009 at 12:01 PM, Mike Williams wrote:
Matt Wozniski wrote:
This sounds like a very good idea to me. I don't know of any other
programs that allow you to change encoding used internally, and we
would be in good company if we chose to always use a unicode encoding
internally
On Tue, Mar 17, 2009 at 4:19 PM, Bram Moolenaar b...@moolenaar.net wrote:
Yakov Lerner wrote:
We have separae highlighting, StatusLineNC, for non-current.
I wish I had different *format*, too, for noncurrent statusline. I do
not think differnt format for non-current statusline is
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
commit e458c019b0ff0515259aebca8e04ce06b9a2646c
Author: Matt Wozniski m
On Thu, Apr 2, 2009 at 2:57 AM, George V. Reilly wrote:
On Wed, Apr 1, 2009 at 11:23 PM, Ron Aaron wrote:
I am currently working on three OSes at the same time: Win32, Linux
and Mac OS/X - and I am using the same vimrc settings on all three.
Mostly the same, anyway.
One area which causes
On Sat, Apr 4, 2009 at 3:17 PM, Yakov Lerner wrote:
If vimscript functions had remark Added in vim7.1.129, it would be useful.
For example, if you want to know how portable the script is.
Probably not exactly what you're looking for, but I keep copies of vim
6.4.10 and 7.0.0 around just so
Bram Moolenaar wrote:
Tony Mechelynck wrote:
Vim is now capable of displaying any Unicode codepoint for which the
installed 'guifont' has a glyph, even outside the BMP (i.e., even above
U+), but there's no easy way to represent those high codepoints by
Unicode value in strings: I mean,
On Fri, Apr 3, 2009 at 11:51 AM, fREW Schmidt wrote:
It looks kosher, leading me to believe it may be some funky
mapping/abbrv you have in place. Do you experience the same
problem when you start with
vim -u NONE
If it does, then you'd have to track down which mapping is
impeding your
On Fri, Apr 10, 2009 at 6:43 PM, Tony Mechelynck wrote:
Couldn't you run test just once? Maybe something more or less like
if test -n $x_includes -a $x_includes != NONE
Just my sense of aesthetics, I'm not on a Mac.
Usually, yes - but lore tells of shells where test isn't POSIX
On Fri, Apr 10, 2009 at 10:53 PM, Tony Mechelynck wrote:
On 11/04/09 04:16, Matt Wozniski wrote:
On Fri, Apr 10, 2009 at 6:43 PM, Tony Mechelynck wrote:
Couldn't you run test just once? Maybe something more or less like
if test -n $x_includes -a $x_includes != NONE
Just my sense
On 4/13/09, Gary Johnson wrote:
On 2009-04-14, Lech Lorens wrote:
The attached patch changes the default 'foldmethod' for the quickfix
window to manual.
I'm a little concerned about applying such fine tuning of individual
window behavior to the source code. If there is a general
On 4/13/09, Tony Mechelynck wrote:
On 14/04/09 00:50, Matt Wozniski wrote:
On 4/13/09, Gary Johnson wrote:
On 2009-04-14, Lech Lorens wrote:
The attached patch changes the default 'foldmethod' for the quickfix
window to manual.
I'm a little concerned about applying such fine tuning
1 - 100 din 134 matches
Mail list logo
