On 2/24/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
-char_u di_key[1]; /* key (actually longer!) */
+char_u di_key[]; /* key (actually longer!) */
I think this is c99 vs c89 difference. C99 allows x[] as last member
of the struct, but c89 does not. As Bram mentioned,
Hi vim-developers!
I have a small bug-report with including fix.
WHAT:
On my home PC the saving of a file always raised two E54 warnings.
Yesterday this was annoying to much (having to press some key before
working on normally, so I investigated a bit. And fixed it =) Open
source is
Hi Bram,
Michael Wookey wrote:
One bug that I didn't fix. Build gvim.exe with OLE=no, run 'gvim -
register',
and watch it crash while trying to display an error message.
This seems to fix the bug...
Index: src/message.c
Hi Bram,
Michael Wookey wrote:
One bug that I didn't fix. Build gvim.exe with OLE=no, run 'gvim
-
register',
and watch it crash while trying to display an error message.
This seems to fix the bug...
Index: src/message.c
When cycling through matches using :cnext, if there are several matches in a
single long line, the line is only shortened the first time (but _not_ the
2nd, 3rd, etc.,) to avoid a Hit-Enter prompt.
Reproducible: every time.
Steps to reproduce:
1. :set wrap I'm not sure this is necessary
2.
Nathan Coulter wrote:
bug report
==
version:
VIM - Vi IMproved 7.0 (2006 May 7, compiled May 7 2006 16:23:43)
MS-Windows 32 bit GUI version with OLE support
problem:
Writing to a file on a windows share where the underlying filesystem
supports hard links, modifying a
On 2/24/07, Larry Alkoff [EMAIL PROTECTED] wrote:
While learning vim 4.6.2
vim 6.4 maybe ?
I typed a control-G to display
the name of the file, number of lines and characters
on the bottom.
What is the command to get out of that mode?
Ctrl-G does not switch modes. Ctrl-G, when typed in
On 2/24/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
I do think that we can do the addition of new people who want to be able
to edit the wiki manually.
Your manual binds here to the addition, correct ? Not to the
edit the wiki, correct, Bram ?
Did you mean here
we can do manual addition of
On 2/6/07, Bram Moolenaar [EMAIL PROTECTED] wrote:
http://google-code-updates.blogspot.com/2007/02/open-source-developers-google-speaker.html
Just watched your presentation. I enjoyed it very much. I think it's
the first time that I saw you speaking and on video. You brought
vi from capable but
Bram Moolenaar wrote:
I think this puts too much burdon the volunteers that become an admin.
And it defeats the easy of use of a wiki.
I was suggesting that people who have a tip, or a change, would
email it to a Vim mailing list, where it would be massaged by the
community, then posted to the
While learning vim 4.6.2 I typed a control-G to display
the name of the file, number of lines and characters
on the bottom.
As Yakov mentioned, it's not a separate mode but just a visual
artifact. You can use control-L to refresh/redraw the screen and
it should clear any such artifacts.
-tim
Hi all,
I setup 2html.com for supporting 256 colors as well
http://www.calmar.ws/tmp/2html.vim
I rather guessed on the grey colors 232-255
the colors 16 - 231 seem to be ok, at least it follows some logic.
Even so, I don't think 16 should be black or should it?
Maybe someone wants to tweak
Hello all,
When using the filetype indentation functionality, setting matchpairs
to the right value will automatically indent after a newline, e.g. in
Java when typing an opening curly brace and then hitting enter the
next line indents according to shiftwidth. The opposite thing happens
when you
John Beckett ([EMAIL PROTECTED]) wrote:
Bram Moolenaar wrote:
I think this puts too much burdon the volunteers that become an admin.
And it defeats the easy of use of a wiki.
I was suggesting that people who have a tip, or a change, would
email it to a Vim mailing list, where it would be
I have noticed when I open a Vim session, my formatoptions and
textwidth variables are reset to the default even though I have the
following lines in my .vimrc file:
set linebreak
set textwidth=80
set formatoptions=ncroqt
Does opening a session prevent Vim from looking at ~/.vimrc?
A secondary
The Vim option 'fileencodings' has some limitations: e.g., it cannot
autodetect GBK and Big5 files at the same time. That was my first
motivation to develop a solution for it. It has two parts: a generic
C++ program to decide the encoding of a file, and a Vim plugin to use
this program.
The
Jeremy Conlin wrote:
I have noticed when I open a Vim session, my formatoptions and
textwidth variables are reset to the default even though I have the
following lines in my .vimrc file:
set linebreak
set textwidth=80
set formatoptions=ncroqt
Does opening a session prevent Vim from looking at
On 2/24/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Jeremy Conlin wrote:
I have noticed when I open a Vim session, my formatoptions and
textwidth variables are reset to the default even though I have the
following lines in my .vimrc file:
set linebreak
set textwidth=80
set
On Sat, Feb 24, 2007 at 03:23:42PM +0100, calmar wrote:
Just in case:
the numbers in 256 terminal and html:
http://www.calmar.ws/tmp/colors.vim.png
http://www.calmar.ws/tmp/htmlcolor216.html
http://www.calmar.ws/tmp/terminalcolors_py.txt (chart)
cheers
calmar
--
(o_ It rocks: LINUX +
Yongwei Wu wrote:
The Vim option 'fileencodings' has some limitations: e.g., it cannot
autodetect GBK and Big5 files at the same time. That was my first
motivation to develop a solution for it. It has two parts: a generic
C++ program to decide the encoding of a file, and a Vim plugin to use
this
[EMAIL PROTECTED] wrote:
John Beckett ([EMAIL PROTECTED]) wrote:
Bram Moolenaar wrote:
I think this puts too much burdon the volunteers that become an admin.
And it defeats the easy of use of a wiki.
I was suggesting that people who have a tip, or a change, would
email it to a Vim mailing
Jeremy Conlin wrote:
On 2/24/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Jeremy Conlin wrote:
I have noticed when I open a Vim session, my formatoptions and
textwidth variables are reset to the default even though I have the
following lines in my .vimrc file:
set linebreak
set
Hi all,
I have two questions regarding the shell (invoked using !) in vim:
(1) Is it possible for the shell to remember what commands I executed in
the original shell window in addition to the commands executed within the
vim shell window?
e.g.
I open up a terminal and type
On 2/24/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Jeremy Conlin wrote:
On 2/24/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Jeremy Conlin wrote:
I have noticed when I open a Vim session, my formatoptions and
textwidth variables are reset to the default even though I have the
following
On 2/24/07, Subramanian Ramaswamy [EMAIL PROTECTED] wrote:
Hi all,
I have two questions regarding the shell (invoked using !) in vim:
(1) Is it possible for the shell to remember what commands I executed in
the original shell window in addition to the commands executed within the
vim shell
Hello all,
I'm trying to find a way to add keywords to the Todo highlight group,
such that they are only highlighted when inside a comment. Reading
through the help files, I thought this would work:
:syntax keyword Todo containedin=Comment contained WARNING NOTE
But unfortunately it doesn't
Jeremy Conlin wrote:
[...]
Tony
Thanks again for all your help. You always have a quick and helpful
response to anyone's questions.
Jeremy
:-) My pleasure. When I don't know the answer, or when someone gave it before
me (and I can see it), I (try to) remain silent ;-).
Best regards,
Thanks, that solves the first half of the question.
Any inputs on how to set something like set -o vi within the vim shell?
Thanks.
On Sat, 24 Feb 2007 12:58:28 -0500, Yakov Lerner [EMAIL PROTECTED] wrote:
On 2/24/07, Subramanian Ramaswamy [EMAIL PROTECTED] wrote:
Hi all,
I have two
Taylor Venable wrote:
Hello all,
I'm trying to find a way to add keywords to the Todo highlight group,
such that they are only highlighted when inside a comment. Reading
through the help files, I thought this would work:
:syntax keyword Todo containedin=Comment contained WARNING NOTE
But
Subramanian Ramaswamy wrote:
Thanks, that solves the first half of the question.
Any inputs on how to set something like set -o vi within the vim shell?
Thanks.
I guess you would have to write it into one of the scripts which
non-interactive non-login shells source at startup (see the
On 2/24/07, Subramanian Ramaswamy [EMAIL PROTECTED] wrote:
Thanks, that solves the first half of the question.
Any inputs on how to set something like set -o vi within the vim shell?
Try one of these:
1. export SHELLOPTS=:vi: # in your .bashrc
or
2. let $SHELLOPTS=vi
-- in your .vimrc
See
On Apr 13, 2006, at 11:30 AM, Andre Massing wrote:
Andre Massing schrieb:
Benji Fisher schrieb:
On Thu, Apr 13, 2006 at 02:50:28PM +0200, André Massing wrote:
Hi All,
I defined an abbrevation :ab NK Newton-Kaskade , but to my
surprise this
abbrevation is not expanded in Insert Mode
Is it possible for gvim to do the same thing as white room?
http://www.hogbaysoftware.com/product/writeroom
it seems like it wouldnt be too hard
1) full screen
2) text centered (like the screenshots in the the URL above)
On Sat, 24 Feb 2007 19:31:23 +0100
A.J.Mechelynck [EMAIL PROTECTED] wrote:
2) The name of the comment syntax group is different for each
language. For instance, it may be vimComment, cComment, htmlComment,
cssComment, etc., depending on what kind of file you're editing. (The
corresponding
Simon Jackson wrote:
Is it possible for gvim to do the same thing as white room?
http://www.hogbaysoftware.com/product/writeroom
it seems like it wouldnt be too hard
1) full screen
2) text centered (like the screenshots in the the URL above)
1) full-screen is easy:
set lines=9
Taylor Venable wrote:
[...]
Thanks for the clarification. I was almost pining for Emacs Lisp
macros there for a second, but Vim came through (as usual). :)
I never could swallow Lisp (maybe because I'm prone to miscount brackets ;-)
). When I want a Polish-notation language for fun, I use
Tim Chase wrote:
While learning vim 4.6.2 I typed a control-G to display
the name of the file, number of lines and characters
on the bottom.
As Yakov mentioned, it's not a separate mode but just a visual
artifact. You can use control-L to refresh/redraw the screen and
it should clear any such
Hi,
Here is the version 1.24:
- Added compatibility with the latest version of php.vim syntax file by Peter
Hodge
(http://www.vim.org/scripts/script.php?script_id=1571)
This fixes wrong indentation and ultra-slow indenting on large php files...
- Fixed spelling in comments.
The indent script
Hi Calmar,
On 2/24/07, calmar [EMAIL PROTECTED] wrote:
Hi all,
I setup 2html.com for supporting 256 colors as well
http://www.calmar.ws/tmp/2html.vim
I rather guessed on the grey colors 232-255
the colors 16 - 231 seem to be ok, at least it follows some logic.
Even so, I don't think 16
Hi Tony,
On 2/25/07, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Yongwei Wu wrote:
The Vim option 'fileencodings' has some limitations: e.g., it cannot
autodetect GBK and Big5 files at the same time. That was my first
motivation to develop a solution for it. It has two parts: a generic
C++
Hello Yongwei,
try FencView.vim
http://www.vim.org/scripts/script.php?script_id=1708
Saturday, February 24, 2007, 11:31:40 PM, you wrote:
?The Vim option 'fileencodings' has some limitations: e.g., it cannot
?autodetect GBK and Big5 files at the same time. That was my first
?motivation to
Yongwei Wu wrote:
[...]
Random French text passed the test, but random Finnish text failed
(got unknown). It seems ää occurs really often in Finnish text.
[...]
Yes indeed: e.g. Hello (wfw. Good day) is hyvää päivää in Finnish. One
of the few phrases I know in that language. ;-)
That's one
:h :saveas
BTW, is it possible somehow to rename file not save as?
hth,
Alan Isaac
--
Best regards, Pavel
43 matches
Mail list logo
