A.J.Mechelynck wrote:
Charles E Campbell Jr wrote:
Victor Hsieh wrote:
[...]
I know. But I just want to read the html code or so with my favoriate
editor ;) I used to do it with vim6. Actually in most case,
connecting to ftp://somewhere (when open http://somewhere) is not
gonna work.
Not
Mike Williams wrote:
mwoehlke did utter on 11/09/2006 18:37:
Mike Williams wrote:
mwoehlke did utter on 11/09/2006 17:44:
Bram Moolenaar wrote:
I don't know what the rules are in all kinds of C, but at least things
like 0x0L, 0x0u, 0x0UL are valid.
Using a match instead of region would
Mike Williams wrote:
mwoehlke did utter on 11/09/2006 17:44:
Bram Moolenaar wrote:
I don't know what the rules are in all kinds of C, but at least things
like 0x0L, 0x0u, 0x0UL are valid.
Using a match instead of region would be simpler.
If one takes KATE's c.xml as canonical, supported
mwoehlke wrote:
Mike Williams wrote:
mwoehlke did utter on 11/09/2006 17:44:
Bram Moolenaar wrote:
I don't know what the rules are in all kinds of C, but at least things
like 0x0L, 0x0u, 0x0UL are valid.
Using a match instead of region would be simpler.
If one takes KATE's c.xml
Nikolai Weibull wrote:
On 9/11/06, mwoehlke [EMAIL PROTECTED] wrote:
mwoehlke wrote:
Mike Williams wrote:
mwoehlke did utter on 11/09/2006 17:44:
Bram Moolenaar wrote:
I don't know what the rules are in all kinds of C, but at least
things
like 0x0L, 0x0u, 0x0UL are valid.
Using a match
Bram Moolenaar wrote:
hundred-and-one symptoms of being an internet addict:
256. You are able to write down over 250 symptoms of being an internet
addict, even though they only asked for 101.
So where is the complete list? ;-)
FIXME and XXX are two common keywords used to mark broken or
Bram Moolenaar wrote:
Patch 7.0.047
Problem:When running configure the exit status is wrong.
Solution: Handle the exit status properly. (Matthew Woehlke)
Files: configure, src/configure
[snip]
Thanks, Bram!
--
Matthew
I blame the hippo.
(On the list, please?)
Rodolfo Borges wrote:
mwoehlke wrote:
A.J.Mechelynck wrote:
Rodolfo Borges wrote:
I made a file with vim commands, starting with
#!/usr/bin/vim -S
so I can execute the file directly, instead of using vim -S file.
The problem is that vim tries to execute this first line
A.J.Mechelynck wrote:
Rodolfo Borges wrote:
I made a file with vim commands, starting with
#!/usr/bin/vim -S
so I can execute the file directly, instead of using vim -S file.
The problem is that vim tries to execute this first line too.
Can we have a workaround on this?
Like, ignoring #! at
Benji Fisher wrote:
On Fri, Jul 21, 2006 at 03:31:15PM -0500, mwoehlke wrote:
Is this possible? It just occurred to me that it would be great if there
was a VIM-related program that would 'cat' in color using VIM's
highlighting rules. Is this something that VIM could be made to do via
Yakov Lerner wrote:
On 7/26/06, mwoehlke [EMAIL PROTECTED] wrote:
Gary Johnson wrote:
I noticed recently that vim does not always set 'filetype' to mail
when I edit mutt temporary files, e.g., postponed messages. I
traced the problem to mutt's use of mktemp() with the pattern
muttXX
Is this possible? It just occurred to me that it would be great if there
was a VIM-related program that would 'cat' in color using VIM's
highlighting rules. Is this something that VIM could be made to do via
scripting, or would it need to be a totally new program? If the latter,
any guesses
A.J.Mechelynck wrote:
mwoehlke wrote:
A.J.Mechelynck wrote:
mwoehlke wrote:
Well, that was exciting... I recently tried to build vim 7 on OSS
(Tandem / HP Nonstop S-Series). I finally got it to work by diff'ing
the ITUG Floss sources (link below) against vim-6.1 and applying the
diffs
Well, that was exciting... I recently tried to build vim 7 on OSS
(Tandem / HP Nonstop S-Series). I finally got it to work by diff'ing the
ITUG Floss sources (link below) against vim-6.1 and applying the diffs
to vim-7.0 (and by first building/installing ncurses-5.5). I would like
to submit my
A.J.Mechelynck wrote:
mwoehlke wrote:
Well, that was exciting... I recently tried to build vim 7 on OSS
(Tandem / HP Nonstop S-Series). I finally got it to work by diff'ing
the ITUG Floss sources (link below) against vim-6.1 and applying the
diffs to vim-7.0 (and by first building/installing
A.J.Mechelynck wrote:
mwoehlke wrote:
I found a really annoying problem trying to build VIM 7 on HP-UX. I
have an automated script that builds VIM as part of a toolchain. It
ran through, and to my surprise and annoyance, installed VIM in
/usr/local instead of where I wanted it.
Long story
(re-send because I forgot to CC vim-dev; sorry)
Bram Moolenaar wrote:
Matthew Woehlke wrote:
[snip]
The indirect 'configure' scripts need to preserve the exit
status.
The fix, which is trivial, I leave as an exercise.
So, what is the fix? I'm lazy.
Goodness, I'll say. :)
I found a really annoying problem trying to build VIM 7 on HP-UX. I have
an automated script that builds VIM as part of a toolchain. It ran
through, and to my surprise and annoyance, installed VIM in /usr/local
instead of where I wanted it.
Long story short, the script called 'configure',
18 matches
Mail list logo
