On Monday 30 April 2007 19:21, A.J.Mechelynck wrote:
John Orr wrote:
Two cents worth - I've long had problems like this, on Suse Linux, where
something, the OS I have assumed, or the X graphics system, takes control
of the sizing of my gvim application.
The size is initially set by my
Thanks for the clarification Brett. At least if you have external commands you
use regularly though, you could wrap them in a vim function, thereby making
them effectively internal, making g useful.
Just an update - I promised I'd investigate extending my patch to help those
people who
Hi all,
I'm a bit frustrated by a particular behaviour of vim, and today I modified the
source code to 'fix' it. I'd be very grateful for some opinions if you
a) agree with my thoughts, or
b) have a better solution.
The problem - is when you run a command that outputs messages to vim - over
Hi Tony, (and others),
Thanks for your (tireless) input, yes, Ctrl-C is certainly a good suggestion,
that works consistently, with no error bells/flashes, no matter how far through
the messages you are.
And I totally agree that it's good to make it easy to know when there is more
output to
Hi all,
I'm using Suse Linux, with KDE, and have a vim function to set my window size
on startup.
The function just sets columns and lines, and calls winpos, depending upon
various other variables I provide.
Previously I was registering this function to be called by an autocmd on the
GUIEnter
:
On Mon, Oct 30, 2006 at 11:30:40AM +1000, John Orr wrote:
Hi all,
I'm using Suse Linux, with KDE, and have a vim function to set my window
size on startup.
The function just sets columns and lines, and calls winpos, depending
upon various other variables I provide.
Previously I
Hi,
I'm wondering if anyone has a good solution to an annoying problem I seem to
cause myself.
When you type a command in vim that results in text scrolling up the screen -
eg :messages or :registers, you will be hit by one of two comments:
Press ENTER or type command to continue
OR
-- More
Have you tried AutoHotKey? It's a brilliant (free) program for writing
powerful macros on windows, trigger by both keyboard and mouse, it must be able
to achieve the desired effect.
On Thursday 03 August 2006 09:09, you wrote:
On 8/2/06, cga2000 [EMAIL PROTECTED] wrote:
On Wed, Aug 02, 2006
Thanks Yakov, and others for the Escape substitute ideas. I'll probably try a
few of them.
John
On Wednesday 02 August 2006 19:13, Yakov Lerner wrote:
On 8/2/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 8/2/06, John Orr [EMAIL PROTECTED] wrote:
When you type a command in vim that results
it for your needs.
Cheers,
John
On Thursday 20 July 2006 11:50, John Orr wrote:
On Thursday 20 July 2006 11:10, [EMAIL PROTECTED] wrote:
What is the easiest way to edit a file that is in the same directory as
the current file? E.g. I open a file like this: vim /x/y/z/w/file1.c and
want to now open
On Thursday 20 July 2006 11:10, [EMAIL PROTECTED] wrote:
What is the easiest way to edit a file that is in the same directory as
the current file? E.g. I open a file like this: vim /x/y/z/w/file1.c and
want to now open /x/y/z/w/file2.c? Occasionally want to open files in
the parent directory
On Wednesday 05 July 2006 12:32, you wrote:
Let's say I have a .filename.swp as the swap file. Is it possible to
automatically recover and store the recovered file as filename.recovered? I
would like to do this non-interactively and for multiple files. Any ideas?
A great question I think -
set listchars+=tab:_
The listchars isn't hugely necessary since the syntax highlighting should point
out any places I failed to tab where I should have, but it can't hurt either.
Thanks again,
John
On Saturday 17 June 2006 05:42, Gerald Lai wrote:
On Fri, 16 Jun 2006, John Orr wrote:
[snip
see a way to tell Vim to indent with tabs sometimes and not others.
On 6/15/06, John Orr [EMAIL PROTECTED] wrote:
Hi,
I'm currently implementing a make system with GNU Make and have been trying
for a while to work out how to get the indentation working as I would like
it to.
I
Hi,
I'm currently implementing a make system with GNU Make and have been trying for
a while to work out how to get the indentation working as I would like it to.
I believe it is reasonably standard when editing makefiles to
set noexpandtab
such that tabs are inserted when you start the
15 matches
Mail list logo
