Re: Thanks for your tireless help

[A.J.Mechelynck]

Michael Henry wrote:

Tony,

I just wanted to write a quick note of thanks for the gigantic number of 
postings you generously provide on the Vim mailing lists.  I'm a 
relative newcomer to Vim, and I've learned a great deal from your 
helpful comments.


:-) Let's say it's compensation on my part, OT1H for not being able to send 
money abroad (to, e.g., Bram's foundation for Uganda), and OTOH from 
frustration at not being able (because I'm not wicked enough) to practice the 
wonderful teaching profession for which I hold a diploma.




Today I responded to a private email from a fellow mailing list reader 
who asked me about compiling Vim for Ubuntu, and I found myself quoting 
from one of your many postings.  I realized that I don't know how to 
pronounce your last name.  This is not a problem when I write email, but 
I'd like to be able to discuss your postings with my co-workers.  Would 
you please clue me in so I can stop calling you 
"Tony-with-the-name-I-can't-pronounce"? :-)


Thanks,
Michael Henry



It depends in which language you pronounce it: (below using IPA, which in turn 
requires Unicode)


fr   : [mɛk'lɛ̃k]or "Antoine mes clinques", rhymes with "cinq".
nl_BE: ['mɛçəlɪŋk]  or "Toone Mechelink" (Flemish pronunciation with -ch- = 
German ich-laut).
nl_NL: ['mɛχəlɪŋk]  or "Toone Mechelink" (Hollands pronunciation with -ch- = 
German ach-laut).

en   : ['mɛklɪŋ]or "Tony Meckling", rhymes with "thing".

On my home page http://users.skynet.be/antoine.mechelynck/ you'll also see 
"Mikhalenko" in Russian (well, as an Ukrainian-looking name), "mahlank" in 
Arabic and "Ma" in Chinese.


The name is originally Flemish but from a French-speaking bourgeois family 
with a long-standing tradition of different pronunciations in (at least) 
French and Flemish.



Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
201. When somebody asks you where you are, you tell them in which chat room.

***SPAM*** Re: Vim70's hignlighting -- Has been solved! thanks all! :)

[yhntgbty]

Hi,all:
Sorry to trouble you all to help me.
I have install a complete Version of Vim7.0,and it has been solved.
Thank you again.

Happy vimming.

yhntgbty


- Original Message - 
From: "Zhaojun WU" <[EMAIL PROTECTED]>
To: "yhntgbty" <[EMAIL PROTECTED]>
Sent: Tuesday, April 10, 2007 2:42 PM
Subject: Re: Vim70's hignlighting


> Hi,
> 
> That's good. :)
> 
> Next time, try to reply or CC to "vim@vim.org" so that others will
> know your problem has been solved and they will not spend time on it
> any more.
> 
> Happy vimming.
> 
> Zhaojun
> 
> On 4/10/07, yhntgbty <[EMAIL PROTECTED]> wrote:
>> Hi,
>> thanks,Zhaojun. I just install a new Ubuntu6.10, the default version of 
>> vim is Vim-7.0-tiny. I have install Vim70 by apt-get
>> Thank you again. :)
>> - Original Message -
>> From: "Zhaojun WU" <[EMAIL PROTECTED]>
>> To: "李长青" <[EMAIL PROTECTED]>
>> Cc: 
>> Sent: Tuesday, April 10, 2007 2:11 PM
>> Subject: Re: ***SPAM*** Re: Re: ***SPAM***_Vim70's hignlighting
>>
>>
>> > Hi,
>> >
>> > Seems you are using Debian? Which package do you choose (I suppose you
>> > installed "vim-tiny" not "vim")? If so, replace the "vim-tiny" with
>> > "vim" via apt-get or aptitude.
>> >
>> > Best,
>> > Zhaojun
>> >
>> > On 4/10/07, 李长青 <[EMAIL PROTECTED]> wrote:
>> >> hi,all:
>> >> thank you.
>> >> I install vim70 as a new software ,not update from other 
>> >> version.
>> >> And there is not a file named vimrc_example.vim at the 
>> >> path /usr/share/vim/vim70,just a file named debian.vim.And when I install 
>> >> vim70 completely,Thers is only one file like *.vim,and only one file 
>> >> named "vimrc" "vimrc.tiny".
>> >>
>> >>
>> >> === 2007-04-10 10:02:48 您在来信中写道：===
>> >>
>> >> >If you updated vim to 7.0 using apt-get, perhpas you could check if the
>> >> >runtimepath also be old in your vimrc.
>> >> >
>> >> >for example, replaced /usr/share/vim/vim64 to /usr/share/vim/vim70
>> >> >
>> >> >李长青 wrote:
>> >> >> hi,all:
>> >> >>I am new to Vim,I am using Vim7.0 now,and it has no Syntax even 
>> >> >> when I set "Syntax on",It stell has no syntax hignlighting,why?  
>> >> >> Please help me. On Vim6.4 ,It has syntax hignlighting, but now 
>> >> >> (vim7.0) it doesn't.
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >> yhntgbty
>> >> >> [EMAIL PROTECTED]
>> >> >> 2007-04-10
>> >> >
>> >>
>> >> = = = = = = = = = = = = = = = = = = = =
>> >>
>> >>
>> >> 致
>> >> 礼！
>> >>
>> >>
>> >> 李长青
>> >> [EMAIL PROTECTED]
>> >> 2007-04-10
>> >>
>> >>
>> >
> 
> 
> -- 
> Best,
> Zhaojun (Joseph)
>

Re: highlighting "weird" characters... Thanks everyone!

[Mitch Wiedemann]

Thanks everyone for your suggestions!  I'm now looking around for a
typical document that I can paste in to use a a guinea pig.

Viva la Vim!

Re: @= (thanks)

[Michael Phillips]

Thanks for replying.  The examples you gave me has help me to understand the
command.  I may not every use it.

Thanks for the info
Michael

--- Tim Chase <[EMAIL PROTECTED]> wrote:

> > Would someone please explain the usage of @=. I am getting
> > confuse from the  help file.
> >
> > [EMAIL PROTECTED]   Matches the preceding atom with zero width. {not in Vi}
> > Like "(?=pattern)" in Perl.
> > Example matches ~
> > foo\(bar\)[EMAIL PROTECTED] "foo" in "foobar"
> > foo\(bar\)[EMAIL PROTECTED] nothing
> > 
> > 
> > To me, the second example matches nothing because there is
> > no foo in between the \( and \)
> > 
> > The first example, I am all confused.  If someone can
> > enlighten me, I would be greatful.
> 
> The pattern
> 
>   \(...\)[EMAIL PROTECTED]
> 
> is interpreted as "make sure that this matches here, but don't 
> consume any of the characters so that things after the '=' begin 
> at the same point as this".
> 
> In the first example, as stated it matches the "foo" in "foobar" 
> because the "bar" can be found after the "foo", but it doesn't 
> become part of the match.  To see this as you're playing around, 
> it's helpful to have
> 
>   :set hls
> 
> so you can see what matches.
> 
> In the second example, the regexp is asking for two disjoint 
> things:  "foo" followed by "bar" and also followed by a second 
> "foo".  It might be more clear if "foo" wasn't used twice:
> 
>   /foo\(bar\)[EMAIL PROTECTED]
> 
> This would match nothing as well, as it asks for "foo" followed 
> immediately by "bar" as well as "foo" followed immediately by "fred".
> 
> For most uses, this isn't very helpful and can be more clearly 
> expressed as
> 
>   /foo\zebar
> 
> where the "\ze" means "and I want the pattern to stop matching here".
> 
> I can concoct crazy uses for the "[EMAIL PROTECTED]" where it might be useful 
> but most of them are refactorable:
> 
>   /foo\([[:print:]]+\)[EMAIL PROTECTED]
> 
> could become
> 
>   /foo[a-z]\ze[[:print:]]*
> 
> One could also use it for crazy filtering:
> 
>   /foo\(\%(.[aeiou]\)\{5}\)[EMAIL PROTECTED]
> 
> This would ensure that you have five pairs of "word-characters 
> (\w) followed by a vowel" following "foo", and that the 4th 
> letter following foo is an "a".  The above could be written 
> without using "[EMAIL PROTECTED]" as something ilke
> 
>   /foo\w[aeiou]\wa\w[aeiou]\w[aeiou]\w[aeiou]
> 
> Readability is in the eye of the beholder. :)  With 2 characters 
> times 5 instances plus 3+1+6, they balance out to about the same. 
>   As those numbers get larger, using the [EMAIL PROTECTED] notation might 
> prove 
> more helpful.
> 
> This allows you to do some pattern intersection (in the 
> set-theory definition of "intersection") which might allow you to 
> shorten the pattern if you have long stretches of things.  It 
> might be helpful in DNA sequencing or something of the like, 
> where one is hunting for certain patterns of A/C/G/T and want to 
> ensure that a certain repeating pattern exists, and then at a 
> certain point in that pattern a given item is more constrained. 
> One might have an alternating sequence where you know you want 
> something like "agct" followed by 75 alternating pairs
> 
>   /agct\(\%([at][cg]\)\{75,}\)[EMAIL PROTECTED]
> 
> You can then tack on "but position 28 through 30 must be 'gag'" 
> (I might be off-by-one here)
> 
>   /agct\(\%([at][cg]\)\{75,}\)[EMAIL PROTECTED](.\{27}gag\)[EMAIL 
> PROTECTED]
> 
> The result will only be the "agct", but it will be followed by 
> the context you need, as there might be many other instances of 
> "agct" that you don't care about because they lack this context.
> 
> (the genetics example chosen as I've seen a couple 
> genetics-searching related questions on the list)
> 
> As cautioned, they're fairly contrived instances, but I hope the 
> above ramblings shed more light than they bewilder, and that 
> using ":set hls" helps see what's considered when using the "[EMAIL 
> PROTECTED]".
> 
> -tim
> 
> 
> 
> 
> 


Michael D. Phillips - A computer science enthusiast
I do not hate Windows, I just like the alternatives better.
Linux is my primary choice.


 

Food fight? Enjoy some healthy debate 
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367

Thanks for Colo(u)red Syntax!

[zzapper]

Hi
Just wanted to thank those involved in colouring syntax.
I've just had a case where I foolishly "ignored" the fact that colouring 
was indicating an error! . I often have Javascript, html, mixed up with Php 
or Coldfusion and yet the colouring works.

And to think when I moved from Vi to VIM I thought that colour was for 
namby-pambies!!

-- 
http://successtheory.com/tips/ Vim, Zsh, MySQL Tips

Re: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[Larry Alkoff]

Just to wind up the string I started.
Titles in vim are now working perfectly.

My current ~/.vimrc contains (in part)
set title
set titleold=""
set titlestring=VIM:\ %F

This works perfectly to display the name of the file I am editing
and returns to a standard titlebar display of
Shell - Konsole <2>
upon exit.

It was the titlestring I had to research to get right.

Thanks to all for your help.

Larry

--
Larry Alkoff N2LA - Austin TX
Using Thunderbird on Linux

Re: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[A.J.Mechelynck]

Larry Alkoff wrote:

Oh silly me.  Now I understand.

After some experimenting I still have some questions.

1.  I'd like to have _only_ the title (or path/title if I must) in the 
titlebar and have the old title restored when I exit vim but I haven't 
yet figured out how to do that after trying various combinations of

set title
set titleold
set titlestring or set titlestring ""

I keep getting the "flying" message.

2.  Where or what are the defaults for  'title' 'titleold' 'titlestring' 
and 'ttybuiltin' so I can have a "typical" title with the current

filename and (if applicable) the "servername".


The defaults are mentioned at the corresponding places in the help. They are 
not set by any .vim scripts but by the C code of Vim itself. The "default" 
value of an option is whatever it is set to if you _don't_ meddle with it. 
That is, remove every ":set" statement for them in your vimrc (and gvimrc) and 
you should get the following default values:


  title " if Vim knows how to restore the title
notitle " otherwise

  titleold=Thanks for flying Vim
" That's the default, but it shouldn't be used

  titlestring=  " having it empty means that Vim must construct
" a «typical» value

  ttybuiltin" TRUE to use the builtin termcap if possible



If I have no entries at all for the above there is no "typical" title 
with filename etc.


Hm...
1) What is the reply to (with question marks as shown)

:verbose set title? titleold? titlestring? ttybuiltin? term?
:echo has("gui_running")

2) What are the first four lines of the output of the ":version" command?



I've changed ~/.vimrc but not /etc/vim/vimrc but there is no 'title' 
string in either of these as delivered so I'm confused as to the defaults.


Larry

[...]



You might try the following values.
THEY ARE GIVEN WITH ABSOLUTELY NO WARRANTY WHATSOEVER, INCLUDING, BUT NOT 
LIMITED TO, MERCHANTABILITY OR FITNESS FOR ANY GENERAL OR PARTICULAR PURPOSE.
In particular, if they beat your dog, abduct your wife, put your house on fire 
and reduce your computer to scrap metal, don't come weep in my jacket.


if !has("gui_running")
set titleold=
if &term == "xterm" && &t_ts == ""
let &t_ts = "\e]2;"
endif
if &t_ts != ""
set title titlestring=%t%m\ -\ VIM
endif
endif



Best regards,
Tony.

Re: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[Larry Alkoff]

Oh silly me.  Now I understand.

After some experimenting I still have some questions.

1.  I'd like to have _only_ the title (or path/title if I must) in the 
titlebar and have the old title restored when I exit vim but I haven't 
yet figured out how to do that after trying various combinations of

set title
set titleold
set titlestring or set titlestring ""

I keep getting the "flying" message.

2.  Where or what are the defaults for  'title' 'titleold' 'titlestring' 
and 'ttybuiltin' so I can have a "typical" title with the current

filename and (if applicable) the "servername".

If I have no entries at all for the above there is no "typical" title 
with filename etc.


I've changed ~/.vimrc but not /etc/vim/vimrc but there is no 'title' 
string in either of these as delivered so I'm confused as to the defaults.


Larry

Max Dyckhoff wrote:

:he means :help, so :he 'title' is suggesting that you read the help file for 
the solution that you need. Including :he 'title' in your .vimrc will upset 
things :)

Max



-Original Message-
From: Larry Alkoff [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006 4:19 PM
To: A.J.Mechelynck
Cc: Yakov Lerner; VIM mail list
Subject: Re: Howto stop "Thanks for flying Vim" on Konsole Window
Titlebar?

A.J.Mechelynck wrote:

Larry Alkoff wrote:

Yakov Lerner wrote:

On 9/21/06, Larry Alkoff <[EMAIL PROTECTED]> wrote:

Whenever I run Vim, the statement
Thanks for flying Vim - Shell - Console
appears on the Konsole Window Titlebar (the blue one at the top).

What is causing this and how can I stop it?

:he 'title'
:he 'titleold'
:he 'titlestring'

Yakov


Thanks Yakow.  I had mistakenly 'set title' in ~/.vimrc.
Commenting it out fixed the problem.

Larry


It may depend on your Vim version and on your running environment. In my
Gnome2 GUI-enabled Vim, I don't set anything but 'title' is set by
default in konsole, and it displays, for instance, "[No Name] + - VIM -
Shell - Konsole" where [No Name] changes to the current filename and +
appears if the file is 'modified'. I have 'term' and $TERM both set to
"xterm" which ought to mean that the title can be restored. I also have
'ttybuiltin' on (the default) which means that the builtin termcap
(which contains a 't_ts' setting for the "xterm" terminal) will be used
in preference to an external termcap or terminfo. In turn, t_ts defined
means that (if the value is correct) the window title can be restored.

Morality: Leave 'title' 'titleold' 'titlestring' and 'ttybuiltin' at
their defaults and you sould have a "typical" title with the current
filename and (if applicable) the "servername". (Note: The reason
'ttybuiltin' is on by default is that, according to Bram, many systems
have fulty termcaps...)


Best regards,
Tony.


After viewing the entire help file, I'm more confused than ever.

In what file should I leave title' 'titleold' 'titlestring' and
'ttybuiltin' at their defaults?

I tried putting:he 'title'
:he 'titleold'
:he 'titlestring'
in ~/.vimrc and vim complains when I try to open a file.

I'm not sure vim is going to let me edit ~/.vimrc again.

Also the help file mentions nothing about something like the above
:he 'string'
Where do these go?  :he means header?

I'm using vim 1:6.4-006+2ubuntu under Kubuntu 6.0.6.

Larry

RE: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[Max Dyckhoff]

:he means :help, so :he 'title' is suggesting that you read the help file for 
the solution that you need. Including :he 'title' in your .vimrc will upset 
things :)

Max


> -Original Message-
> From: Larry Alkoff [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 21, 2006 4:19 PM
> To: A.J.Mechelynck
> Cc: Yakov Lerner; VIM mail list
> Subject: Re: Howto stop "Thanks for flying Vim" on Konsole Window
> Titlebar?
>
> A.J.Mechelynck wrote:
> > Larry Alkoff wrote:
> >> Yakov Lerner wrote:
> >>> On 9/21/06, Larry Alkoff <[EMAIL PROTECTED]> wrote:
> >>>> Whenever I run Vim, the statement
> >>>> Thanks for flying Vim - Shell - Console
> >>>> appears on the Konsole Window Titlebar (the blue one at the top).
> >>>>
> >>>> What is causing this and how can I stop it?
> >>>
> >>> :he 'title'
> >>> :he 'titleold'
> >>> :he 'titlestring'
> >>>
> >>> Yakov
> >>>
> >>
> >> Thanks Yakow.  I had mistakenly 'set title' in ~/.vimrc.
> >> Commenting it out fixed the problem.
> >>
> >> Larry
> >>
> >
> > It may depend on your Vim version and on your running environment. In my
> > Gnome2 GUI-enabled Vim, I don't set anything but 'title' is set by
> > default in konsole, and it displays, for instance, "[No Name] + - VIM -
> > Shell - Konsole" where [No Name] changes to the current filename and +
> > appears if the file is 'modified'. I have 'term' and $TERM both set to
> > "xterm" which ought to mean that the title can be restored. I also have
> > 'ttybuiltin' on (the default) which means that the builtin termcap
> > (which contains a 't_ts' setting for the "xterm" terminal) will be used
> > in preference to an external termcap or terminfo. In turn, t_ts defined
> > means that (if the value is correct) the window title can be restored.
> >
> > Morality: Leave 'title' 'titleold' 'titlestring' and 'ttybuiltin' at
> > their defaults and you sould have a "typical" title with the current
> > filename and (if applicable) the "servername". (Note: The reason
> > 'ttybuiltin' is on by default is that, according to Bram, many systems
> > have fulty termcaps...)
> >
> >
> > Best regards,
> > Tony.
> >
>
> After viewing the entire help file, I'm more confused than ever.
>
> In what file should I leave title' 'titleold' 'titlestring' and
> 'ttybuiltin' at their defaults?
>
> I tried putting:he 'title'
> :he 'titleold'
> :he 'titlestring'
> in ~/.vimrc and vim complains when I try to open a file.
>
> I'm not sure vim is going to let me edit ~/.vimrc again.
>
> Also the help file mentions nothing about something like the above
> :he 'string'
> Where do these go?  :he means header?
>
> I'm using vim 1:6.4-006+2ubuntu under Kubuntu 6.0.6.
>
> Larry
>
>
>
>
> --
> Larry Alkoff N2LA - Austin TX
> Using Thunderbird on Linux

Re: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[Larry Alkoff]

A.J.Mechelynck wrote:

Larry Alkoff wrote:

Yakov Lerner wrote:

On 9/21/06, Larry Alkoff <[EMAIL PROTECTED]> wrote:

Whenever I run Vim, the statement
Thanks for flying Vim - Shell - Console
appears on the Konsole Window Titlebar (the blue one at the top).

What is causing this and how can I stop it?


:he 'title'
:he 'titleold'
:he 'titlestring'

Yakov



Thanks Yakow.  I had mistakenly 'set title' in ~/.vimrc.
Commenting it out fixed the problem.

Larry



It may depend on your Vim version and on your running environment. In my 
Gnome2 GUI-enabled Vim, I don't set anything but 'title' is set by 
default in konsole, and it displays, for instance, "[No Name] + - VIM - 
Shell - Konsole" where [No Name] changes to the current filename and + 
appears if the file is 'modified'. I have 'term' and $TERM both set to 
"xterm" which ought to mean that the title can be restored. I also have 
'ttybuiltin' on (the default) which means that the builtin termcap 
(which contains a 't_ts' setting for the "xterm" terminal) will be used 
in preference to an external termcap or terminfo. In turn, t_ts defined 
means that (if the value is correct) the window title can be restored.


Morality: Leave 'title' 'titleold' 'titlestring' and 'ttybuiltin' at 
their defaults and you sould have a "typical" title with the current 
filename and (if applicable) the "servername". (Note: The reason 
'ttybuiltin' is on by default is that, according to Bram, many systems 
have fulty termcaps...)



Best regards,
Tony.



After viewing the entire help file, I'm more confused than ever.

In what file should I leave title' 'titleold' 'titlestring' and 
'ttybuiltin' at their defaults?


I tried putting:he 'title'
:he 'titleold'
:he 'titlestring'
in ~/.vimrc and vim complains when I try to open a file.

I'm not sure vim is going to let me edit ~/.vimrc again.

Also the help file mentions nothing about something like the above
:he 'string'
Where do these go?  :he means header?

I'm using vim 1:6.4-006+2ubuntu under Kubuntu 6.0.6.

Larry




--
Larry Alkoff N2LA - Austin TX
Using Thunderbird on Linux

Re: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[A.J.Mechelynck]

Larry Alkoff wrote:

Yakov Lerner wrote:

On 9/21/06, Larry Alkoff <[EMAIL PROTECTED]> wrote:

Whenever I run Vim, the statement
Thanks for flying Vim - Shell - Console
appears on the Konsole Window Titlebar (the blue one at the top).

What is causing this and how can I stop it?


:he 'title'
:he 'titleold'
:he 'titlestring'

Yakov



Thanks Yakow.  I had mistakenly 'set title' in ~/.vimrc.
Commenting it out fixed the problem.

Larry



It may depend on your Vim version and on your running environment. In my 
Gnome2 GUI-enabled Vim, I don't set anything but 'title' is set by 
default in konsole, and it displays, for instance, "[No Name] + - VIM - 
Shell - Konsole" where [No Name] changes to the current filename and + 
appears if the file is 'modified'. I have 'term' and $TERM both set to 
"xterm" which ought to mean that the title can be restored. I also have 
'ttybuiltin' on (the default) which means that the builtin termcap 
(which contains a 't_ts' setting for the "xterm" terminal) will be used 
in preference to an external termcap or terminfo. In turn, t_ts defined 
means that (if the value is correct) the window title can be restored.


Morality: Leave 'title' 'titleold' 'titlestring' and 'ttybuiltin' at 
their defaults and you sould have a "typical" title with the current 
filename and (if applicable) the "servername". (Note: The reason 
'ttybuiltin' is on by default is that, according to Bram, many systems 
have fulty termcaps...)



Best regards,
Tony.

Re: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[Larry Alkoff]

Yakov Lerner wrote:

On 9/21/06, Larry Alkoff <[EMAIL PROTECTED]> wrote:

Whenever I run Vim, the statement
Thanks for flying Vim - Shell - Console
appears on the Konsole Window Titlebar (the blue one at the top).

What is causing this and how can I stop it?


:he 'title'
:he 'titleold'
:he 'titlestring'

Yakov



Thanks Yakow.  I had mistakenly 'set title' in ~/.vimrc.
Commenting it out fixed the problem.

Larry

--
Larry Alkoff N2LA - Austin TX
Using Thunderbird on Linux

Re: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[Yakov Lerner]

On 9/21/06, Larry Alkoff <[EMAIL PROTECTED]> wrote:

Whenever I run Vim, the statement
Thanks for flying Vim - Shell - Console
appears on the Konsole Window Titlebar (the blue one at the top).

What is causing this and how can I stop it?


:he 'title'
:he 'titleold'
:he 'titlestring'

Yakov

Re: Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[Charles E Campbell Jr]

Larry Alkoff wrote:


Whenever I run Vim, the statement
Thanks for flying Vim - Shell - Console
appears on the Konsole Window Titlebar (the blue one at the top).

What is causing this and how can I stop it?


:help titleold

Regards,
Chip Campbell

Howto stop "Thanks for flying Vim" on Konsole Window Titlebar?

[Larry Alkoff]

Whenever I run Vim, the statement
Thanks for flying Vim - Shell - Console
appears on the Konsole Window Titlebar (the blue one at the top).

What is causing this and how can I stop it?

Larry

--
Larry Alkoff N2LA - Austin TX
Using Thunderbird on Linux

Re: VIM7.0: How to switch off the spell check function? Thanks a lot.

[Japerlh]

Thanks a lot for all you guys.

On 5/10/06, Pete Johns <[EMAIL PROTECTED]> wrote:

On Tue, 2006-05-09 at 11:50:29 +0800, Japerlh sent:
>VIM7.0: How to switch off the spell check function?
>
>The following command can be used to switch on the spell check.
>What is the command to turn it off?
>   :setlocal spell spelllang=en_us
>
I have the following in my .vimrc:

"""" Toggle Vim v7.0 Spell-Checking.
if (v:version >= 700)
set spell spelllang=en_au
nnoremap  :set spell! spell?
imap  
vmap  
endif

Hope this helps;


--paj
--
Pete Johns   <http://johnsy.com/>
Tel/Fax numbers and IM information   <http://johnsy.com/contact/>
May The Fourth Be With You F...<http://johnsy.com/20060504164831>






--

Besh wishes,
Japerlh

Re: VIM7.0: How to switch off the spell check function? Thanks a lot.

[Pete Johns]

On Tue, 2006-05-09 at 11:50:29 +0800, Japerlh sent:
>VIM7.0: How to switch off the spell check function?
>
>The following command can be used to switch on the spell check.
>What is the command to turn it off?
>   :setlocal spell spelllang=en_us
>
I have the following in my .vimrc:

 Toggle Vim v7.0 Spell-Checking.
if (v:version >= 700)
set spell spelllang=en_au
nnoremap  :set spell! spell?
imap  
vmap  
endif

Hope this helps;


--paj
-- 
Pete Johns   
Tel/Fax numbers and IM information   
May The Fourth Be With You F...


pgp6lvGk15f1V.pgp
Description: PGP signature

Re: VIM7.0: How to switch off the spell check function? Thanks a lot.

[Mikolaj Machowski]

Dnia wtorek, 9 maja 2006 05:50, Japerlh napisał:
> VIM7.0: How to switch off the spell check function?
>
> The following command can be used to switch on the spell check.
> What is the command to turn it off?
>
>   :setlocal spell spelllang=en_us

Switch state of boolean options::

:set spell!

m.

Re: VIM7.0: How to switch off the spell check function? Thanks a lot.

[Ricky Zhou]

On 5/8/06, Japerlh <[EMAIL PROTECTED]> wrote:

VIM7.0: How to switch off the spell check function?

I think the commands are:
Enable- :set spell
Disable- :set nospell

VIM7.0: How to switch off the spell check function? Thanks a lot.

[Japerlh]

VIM7.0: How to switch off the spell check function?

The following command can be used to switch on the spell check.
What is the command to turn it off?
:setlocal spell spelllang=en_us

Thanks a lot.


--

Besh wishes,
Japerlh

Re: Font names - THANKS!

[dax2]

On Mon, 24 Apr 2006 15:29:26 +0200
Andrei wrote:
[...][This isn't a quote, I have edited a bit for the Sony/misc-12x24]
> 
> 
> Fixed
> 
>  compare="not_eq">
> 17
> 
> 
> 
> /usr/X11R6/lib/X11/fonts/misc/12x24.pcf.gz
> 
> 
> 87
> 
> 
> false
> 
> 
> 
> With that added, I can request "Fixed" and get the desired font. If I'm
> requesting "Fixed 12" then I get the scalable TTF. Maybe you can do
> something similar to your local.conf or ~/.fonts.conf to force
> fontconfig to return the desired font when you request "monospace 24".

I have edited your suggestion (not much) and that was it.

THANK YOU! That was a nice help, it works instantly. I chose to call
it "Fixed 17" because as far as I know it is a 17pt (or 18pt?) font;
but that doesn't make much sense by the way because the size of the
font changes with screen-resolution.

I did not know how font-config works, and now know a little more,
which is good. Why is "style" and "strong" given the value "87"?


   Donald

-- 
dax2-tele2adsl:dk -- http://d-axel.dk/  Donald Axel