Edward L. Fox wrote:
> Hi Tony,
>
> On 8/16/07, Tony Mechelynck <[EMAIL PROTECTED]> wrote:
>> Chris Sutcliffe wrote:
>>> Replied direct to Bram instead of the list...
>>>
>>> On 8/15/07, Chris Sutcliffe wrote:
> Adding (char *) casts for things that are already character strings?
> Isn't
Hi Bram,
If I undo a change, and then do
undojoin | delete
I get an error. Perhaps you could add a "undojoin!" command that
silently ignores the "undojoin" if the previous operation was an undo.
I currently (in scripts) have to do something like
try
undojoin |
catch
On 8/16/07, Xiaozhou Liu <[EMAIL PROTECTED]> wrote:
>
> Hi Edward,
>
> Patch 7.1.071 adds test64 into src/testdir/. But it is not there
> as I browse the subversion repository below. Is there any problem
> or am I wrong?
I see... Thanks very much for your report. As I'm not able to access
the In
On 8/16/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>
>
> Xiaozhou Liu wrote:
>
> > Patch 7.1.071 adds test64 into src/testdir/. But it is not there
> > as I browse the subversion repository below. Is there any problem
> > or am I wrong?
> >
> > https://vim.svn.sourceforge.net/svnroot/vim/branc
Hi Tony,
On 8/16/07, Tony Mechelynck <[EMAIL PROTECTED]> wrote:
>
> Chris Sutcliffe wrote:
> > Replied direct to Bram instead of the list...
> >
> > On 8/15/07, Chris Sutcliffe wrote:
> >>> Adding (char *) casts for things that are already character strings?
> >>> Isn't this a problem in gcc?
> >
Chris Sutcliffe wrote:
> Replied direct to Bram instead of the list...
>
> On 8/15/07, Chris Sutcliffe wrote:
>>> Adding (char *) casts for things that are already character strings?
>>> Isn't this a problem in gcc?
>> GCC complains that const char*'s is being passed as a char*'s (because
>> it's
Replied direct to Bram instead of the list...
On 8/15/07, Chris Sutcliffe wrote:
> > Adding (char *) casts for things that are already character strings?
> > Isn't this a problem in gcc?
>
> GCC complains that const char*'s is being passed as a char*'s (because
> it's a contant string being passe
Bram Moolenaar wrote:
> Tony Mechelynck wrote:
>
>> g8 doesn't work properly in 7.1.079
>>
>> Reproducible: Always
>>
>> Steps to reproduce:
>> 1. Insert the Pilcrow mark into a buffer with 'encoding' and 'fileencoding'
>> both set to utf-8 (e.g. using ^KPI ).
>> 2. Go back to Normal mode
>> 3. P
Chris Sutcliffe wrote:
> Below is a small patch for GvimExt to correct some warnings when
> compiled with GCC 4.
>
> Index: gvimext.cpp
> ===
> RCS file: /cvsroot/vim/vim7/src/GvimExt/gvimext.cpp,v
> retrieving revision 1.6
> diff
Tony Mechelynck wrote:
> g8 doesn't work properly in 7.1.079
>
> Reproducible: Always
>
> Steps to reproduce:
> 1. Insert the Pilcrow mark into a buffer with 'encoding' and 'fileencoding'
> both set to utf-8 (e.g. using ^KPI ).
> 2. Go back to Normal mode
> 3. Place the cursor on the character
Please ignore my two latest posts to vim-dev. For some reason 'encoding' had
been set to latin1 without my say-so. This may still be a bug in :mksession,
albeit a different one.
Best regards,
Tony.
--
Build a better mousetrap, the saying goes -- and with the brassiere,
Yankee Ingenuity did exa
g8 doesn't work properly in 7.1.079
Reproducible: Always
Steps to reproduce:
1. Insert the Pilcrow mark into a buffer with 'encoding' and 'fileencoding'
both set to utf-8 (e.g. using ^KPI ).
2. Go back to Normal mode
3. Place the cursor on the character inserted at step 1.
4. Hit g8
Actual resu
:mksession (in 7.1.077) or gvim -S (in 7.1.079) doesn't work properly in UTF-8
locale with Unicode codepoints (> U+007F) in 'listchars'
gvim 7.1.077 in UTF-8 locale
[...]
:set lcs=tab:\|_,eol:¶,nbsp:~
[...]
:mks!
:qa
(patch to 7.1.079, make, make install)
gvim -S
Error det
Bram Moolenaar wrote:
>Charles Campbell wrote:
>
>
>
>>I'd like to do
>>
>> imap ... = ...=:something
>>
>>however, "." no longer repeats the small change. For example:
>>
>> imap = =:echo "hello!"
>>
>>work with the following file contents:
>>
>>abc;
>>def;
>>
>>Place cursor on the semicol
Tony asked:
>Bram Moolenaar wrote:
>>
>> How about using CTRL-G CTRL-O for going to Normal mode without
>> breaking the current Insert in two? It would only work when
>> the cursor didn't move and the text isn't changed.
>>
>
> I don't find Ctrl-G Ctrl-O under ":help ins-spe
Bram Moolenaar wrote:
>
> Charles Campbell wrote:
>
>> I'd like to do
>>
>>imap ... = ...=:something
>>
>> however, "." no longer repeats the small change. For example:
>>
>> imap = =:echo "hello!"
>>
>> work with the following file contents:
>>
>> abc;
>> def;
>>
>> Place cursor on the s
Charles Campbell wrote:
> I'd like to do
>
>imap ... = ...=:something
>
> however, "." no longer repeats the small change. For example:
>
> imap = =:echo "hello!"
>
> work with the following file contents:
>
> abc;
> def;
>
> Place cursor on the semicolon with "abc;" -- insert
> =
Yakov Lerner wrote:
> Undo after retab modifies 'tabstop' in a way that doesn't look consistent or
> correct.
> Test case:
> -
> vim -u NONE -U NONE
> iabc
> :set ts=4
> :retab 8
> u
> --
> After the last u, tabstop changes to 8. Bu
Xiaozhou Liu wrote:
> Patch 7.1.071 adds test64 into src/testdir/. But it is not there
> as I browse the subversion repository below. Is there any problem
> or am I wrong?
>
> https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1/src/testdir/
Subversion always lags behind, between a few
Patch 7.1.079
Problem:When the locale is "C" and 'encoding' is "latin1" then the "@"
character in 'isfname', 'isprint', etc. doesn't pick up accented
characters.
Solution: Instead of isalpha() use MB_ISLOWER() and MB_ISUPPER().
Files: src/charset.c, src/macros.h
Hey,
Below is a small patch for GvimExt to correct some warnings when
compiled with GCC 4.
Index: gvimext.cpp
===
RCS file: /cvsroot/vim/vim7/src/GvimExt/gvimext.cpp,v
retrieving revision 1.6
diff -u -r1.6 gvimext.cpp
--- gvimext.cp
Antony Scriven wrote:
>
>Maybe. Could you use something like this as a workaround?
>
>fun! Echo()
> echo 'hello!'
> sleep 1 |" just to make the effect visible
> return ''
>endfun
>imap = ==Echo()
>
>
Hmm -- I definitely have a blind spot with = stuff. Thanks, Antony
-- I think it just m
On 15/08/07, Charles E Campbell Jr <[EMAIL PROTECTED]> wrote:
> Hello!
>
> I'd like to do
>
>imap ... = ...=:something
>
> however, "." no longer repeats the small change. For example:
>
> imap = =:echo "hello!"
>
> work with the following file contents:
>
> abc;
> def;
>
>
On 2007-08-15, Andrew Myers <[EMAIL PROTECTED]> wrote:
> On Aug 15, 2007, at 3:21 AM, Matthew Winn wrote:
> >
> > I get the impression that the OP doesn't want right-aligned text, but
> > wants a better distribution of ragged-right lines. For example,
> > consider the first two lines of this parag
Patch 7.1.078
Problem:Dropping a file name on gvim that contains a CSI byte doesn't work
when editing the command line.
Solution: Escape the CSI byte when inserting in the input buffer. (Yukihiro
Nakadaira)
Files: src/gui.c, src/ui.c
*** ../vim-7.1.077/src/gui
On Wed 15-Aug-07 9:59am -0600, Yakov Lerner wrote:
> Undo after retab modifies 'tabstop' in a way that doesn't look consistent or
> correct.
> Test case:
> -
> vim -u NONE -U NONE
> iabc
> :set ts=4
> :retab 8
> u
> --
> After the
Hi Edward,
Patch 7.1.071 adds test64 into src/testdir/. But it is not there
as I browse the subversion repository below. Is there any problem
or am I wrong?
https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.1/src/testdir/
Thanks,
Xiaozhou
--~--~-~--~~~---~-
Georg Dahn wrote:
> Andrew Myers wrote:
>> Actually, I think I would make the strong claim that what I am
>> talking about is not just some personal preference, but a fairly
>> universal one. All serious text formatting systems try to make line
>> lengths equal (without introducing additiona
Hello!
I'd like to do
imap ... = ...=:something
however, "." no longer repeats the small change. For example:
imap = =:echo "hello!"
work with the following file contents:
abc;
def;
Place cursor on the semicolon with "abc;" -- insert
=2
Now put the cursor on the semicolon with "def
Undo after retab modifies 'tabstop' in a way that doesn't look consistent or
correct.
Test case:
-
vim -u NONE -U NONE
iabc
:set ts=4
:retab 8
u
--
After the last u, tabstop changes to 8. But we expect the screen
to return to the state
On Aug 15, 2007, at 3:21 AM, Matthew Winn wrote:
>
> I get the impression that the OP doesn't want right-aligned text, but
> wants a better distribution of ragged-right lines. For example,
> consider the first two lines of this paragraph. The naïve breaking
> algorithm used by my mail client has l
On 10/08/2007 09:58, Mike Williams wrote:
> On 10/08/2007 02:01, Ilya Bobir wrote:
>> Ilya Bobir wrote:
>>> [...]
>>>
>>> It does work on NT. But CreateProcess(..., CREATE_NO_WINDOW, ...) is
>>> needed. An example implementation is attached.
>>>
>> I've just found slightly different approach
Adri Verhoef wrote:
> On Sun, Aug 12, 2007 at 14:55:48 +, Bram Moolenaar wrote:
> > Patch 7.1.068
> > --- runtime/doc/options.txt Sat Aug 11 17:25:38 2007
> > ! 4. one of the other windows are wider than the current or new
> > ! window.
>
> Should be: ...one of the ot
Andrew Myers wrote:
> Actually, I think I would make the strong claim that what I am
> talking about is not just some personal preference, but a fairly
> universal one. All serious text formatting systems try to make line
> lengths equal (without introducing additional line breaks), because
On Tue, 14 Aug 2007 18:55:53 -0700, Gary Johnson
<[EMAIL PROTECTED]> wrote:
> I believe the studies that have shown fully-justified text to be
> easier to read than left-justified (ragged-right) text used
> proportional fonts properly typeset on a printed page.
>
> Vim uses a mono-spaced font.
35 matches
Mail list logo
