[EMAIL PROTECTED] wrote:
Steve Hall [EMAIL PROTECTED] 写于 2007-05-29 12:19:43:
You could say that top posting is easier to write, but bottom posting
is easier to read. The extra effort of one poster saves all the
readers the same amount of effort. For a group, bottom posting keeps
everyone on
[EMAIL PROTECTED] wrote:
In the end, what's preferred is personal despite arguments pro and con.
However, the preponderant opinion and therefore usage in the Vim group
is bottom-posting, though many use interspersed posting and get away
with it. If you don't bottom-post, you get told about
linda.s wrote:
After clicking the user manuual under help, I wonder which command can
be used to open these help txt in the manual?
Since you said something about clicking, I'll assume you're using a
GUI version of vim.
You should be able to simply double-click on any of the help files you
see
fREW wrote:
On 5/22/07, fREW [EMAIL PROTECTED] wrote:
On 5/22/07, Gene Kwiecinski [EMAIL PROTECTED] wrote:
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B
[EMAIL PROTECTED] wrote:
It seems nature to have vim behave like vi, if the Linux distribution
choose to do so. The distribution decides everything and it is non-related
to vim developers themselves.
All you need to do is to: sudo apt-get install vim-gtk, which installs a
Big version of
Bram Moolenaar wrote:
Patch 7.1.002
Problem:Oracle Pro*C/C++ files are not detected.
Solution: Add the missing star. (Micah J. Cowan)
Just to be clear: while I reformatted the solution in patch-form, it was
Arturo Olguín Cruz who first found the bug and determined its fix:
Thomas Michael Engelke wrote:
Hello Tony, and thanks for your extensive answer. Unfortunately, this
is what I can report. To make things easier, I'll attach the file I am
talking about to this message so that you can either check for
yourselves and/or see that I'm telling the truth.
What is
Jeenu V wrote:
Hi Vimmers,
I'm using VIM (version 6.2) through putty. The digraphs that are
displayed (either through :dig command or CTRL-K insertions) are all
weird characters. When I tried to use digraphs as fold markers, it
worked, but the fold markers inserted are still those weird
Thomas Michael Engelke wrote:
But that's arguing semantics when the core of the problem is known
now. I apologize for having a different set of mind and not
understanding the problem instantly.
This is not a fair remark, considering I pointed out to you, privately,
that he made the statement
Thomas Michael Engelke wrote:
2007/5/15, Micah Cowan [EMAIL PROTECTED]:
Thomas Michael Engelke wrote:
But that's arguing semantics when the core of the problem is known
now. I apologize for having a different set of mind and not
understanding the problem instantly.
This is not a fair
Gene Kwiecinski wrote:
fileformats=dos,unix, so both formats are available, yet the
detection and switching does not seem to work.
Are you sure _every_ line ends in ^M?
Positive. Every single line shows an ^M at the end. set fileformat
gives unix after loading. Setting fileformat to dos
Fixes an apparent typo in filetype.vim.
Per https://bugs.launchpad.net/ubuntu/+source/vim/+bug/86916.
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
Index: runtime/filetype.vim
linda.s wrote:
Hi,
I am a beginner in VIM. Wonder whether there is any good book for VIM?
Also, what is the difference between vim and latex?
Linda, I've personally found the vim tutorial to be a quite-adequate
means to learning vim. Just type vimtutor in your terminal, and you're
good to go!
Bram Moolenaar wrote:
Micah Cowan wrote:
Following description lifted from bug filed at
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/78960
[EMAIL PROTECTED]:~$ rm .viminfo
[EMAIL PROTECTED]:~$ ln -s /dev/null .viminfo
[EMAIL PROTECTED]:~$ ls -l .viminfo
lrwxrwxrwx 1 sa sa 9 2007
A.J.Mechelynck wrote:
Micah Cowan wrote:
Bram Moolenaar wrote:
[...]
The solution is simple: Don't create a link in place of the .viminfo
file. And certainly not to /dev/null.
Background info: When Vim finds an existing .viminfo file, it writes the
new info into a temp file (since it's
Informationen wrote:
Hi,
could somebody tell me how to type complex Greek characters like ῷ or ἅ. I am
using vim7.0 with multibyte and myltilang enabled on Kubuntu 6.06. In other
applications I change the language to polytonic greek and use a composer key.
Is there a similar way in vim
Following description lifted from bug filed at
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/78960
[EMAIL PROTECTED]:~$ rm .viminfo
[EMAIL PROTECTED]:~$ ln -s /dev/null .viminfo
[EMAIL PROTECTED]:~$ ls -l .viminfo
lrwxrwxrwx 1 sa sa 9 2007-01-12 17:16 .viminfo - /dev/null
[EMAIL
Bram Moolenaar wrote:
Micah Cowan wrote:
Towards a better solution: how straightforward do you think it'll be to
talk the ncurses guys into adding support for some of screen's
extensions? AFAIK, the only one I care about is the xterm mouse support;
another interesting one is a boolean
Copying the dev list. The missing context is that running vim via sudo
before having run it as regular user, causes permission problems with
the created .viminfo file (and others?).
Vincent BEFFARA wrote:
Wonderful, the problem really is about permission of .viminfo!
I noticed that you
Copying the dev list. The missing context is that running vim via sudo
before having run it as regular user, causes permission problems with
the created .viminfo file (and others?).
Vincent BEFFARA wrote:
Wonderful, the problem really is about permission of .viminfo!
I noticed that you
lin q wrote:
Great, this works.
Another question, :tabe % can open the same file, is there an easy way
to open another file which locates in the same or very similar directory
of the current file?
For example, I am viewing f2 now, and I want to open f3 which is of same
directory of f2
Bram Moolenaar wrote:
Micah Cowan wrote:
Vincent BEFFARA wrote:
However, it would be nice of vim to always test that it owns the $HOME
directory before creating files there. Would it break anything ?
I think this would be a good idea as well. One could argue that if we
reason this way
I wrote:
Therefore, there would seem to be no harm whatsoever in detecting screen
as an xterm-mouse-code-capable terminal, and sending the mouse-mode
sequence (xterm protocol, since AFAIK screen provides no way to detect
the underlying xterm version). If the underlying terminal claims to be
A.J.Mechelynck wrote:
Micah Cowan wrote:
Attached is a proposed patch that effects the change I'm requesting. I
would love to get some feedback/further discussion based on it. They say
code talks, and so here is my concrete expression. :)
Shouldn't it rather use the 'ttymouse' option
A.J.Mechelynck wrote:
This is done as a result
of sending the t_RV code and receiving an answer for it, which happens
after the first file has been loaded and all -c commands have been
processed: probably just before or just after the VimEnter event. IOW,
you cannot test them in your vimrc
Micah Cowan wrote:
A.J.Mechelynck wrote:
This is done as a result
of sending the t_RV code and receiving an answer for it, which happens
after the first file has been loaded and all -c commands have been
processed: probably just before or just after the VimEnter event. IOW,
you cannot test
Sorry for the repost; but I realized I should've drawn more attention to
the message with the patch in it, both so other lurkers know the thread
now includes a proposed patch, and so that we know what message to go
back to if we want to refer to the code we're discussing.
I have made a slight
Yakov Lerner wrote:
On 5/9/07, Edward L. Fox [EMAIL PROTECTED] wrote:
If you had checked out a copy of the sources before, please run this
command in your source root directory to switch into the current
branch:
svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1
This
Bram Moolenaar wrote:
Micah Cowan wrote:
Sorry for the repost; but I realized I should've drawn more attention to
the message with the patch in it, both so other lurkers know the thread
now includes a proposed patch, and so that we know what message to go
back to if we want to refer
Gary Johnson wrote:
On 2007-05-09, Micah Cowan [EMAIL PROTECTED] wrote:
Towards a better solution: how straightforward do you think it'll be to
talk the ncurses guys into adding support for some of screen's
extensions? AFAIK, the only one I care about is the xterm mouse support;
another
Yakov Lerner wrote:
On 5/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
When opening a file in vim, the cursor will move to the last position
when
the file was saved.
The simplest way to fix this is to add this line to your .vimrc:
$VIMRUNTIME/vimrc_example.vim
Another, more
A.J.Mechelynck wrote:
AFAIK, there is no list-admin; just the mail robot. Or if there is one,
he only reads the list when the moon is blue on the 4th Thursday of a
week, and I don't know his phone number (if any).
The Vim mailing list page (http://www.vim.org/maillist.php) mentions
[EMAIL
Yakov Lerner wrote:
On 5/9/07, Edward L. Fox [EMAIL PROTECTED] wrote:
If you had checked out a copy of the sources before, please run this
command in your source root directory to switch into the current
branch:
svn switch https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1
This
[EMAIL PROTECTED] wrote:
Vincent BEFFARA [EMAIL PROTECTED] 写于 2007-05-09 23:54:27:
Hi,
Recently I installed Ubuntu Feisty and the feature seems to have
gone (I
installed vim-gnome version 7.0.135). Since I use the same .vimrc in
all
platform, it is unlikely to be the fault of my .vimrc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Some folks who like to use vim under GNU screen, myself included, would
like the ability for vim to automatically support xterm mouse escape
sequences. Would it be a workable solution for vim to include screen
as one of the initial strings for
Doh! I accidentally sent this directly to Bram, instead of to list :/
Bram Moolenaar wrote:
I'm guessing that a problem for this, might be the fact that if vim
detects xterm-ish terminals, it automatically tries the t_RV sequence
out, which isn't dependably valid for screen.
If this is the
A.J.Mechelynck wrote:
Micah Cowan wrote:
[...]
But you already have hacked support into your programs for mouse
support. Now that you've done that, couldn't you just open it up a bit?
Is there anything wrong with always recognizing the appropriate xterm
sequences (provided that they don't
A.J.Mechelynck wrote:
Micah Cowan wrote:
[...]
But you already have hacked support into your programs for mouse
support. Now that you've done that, couldn't you just open it up a bit?
Is there anything wrong with always recognizing the appropriate xterm
sequences (provided that they don't
38 matches
Mail list logo
