On 8/31/05, Zdenek SEKERA <Zdenek.Sekera@...> wrote:
  >1. when I do e.g. ':verbose function', I get a very long listing of
  >    quite long lines that wrap around. e.g.: (just a short example):
  >    Clearly, it outputs the function itself as well. Maybe that's
  >    what's wanted but I don't like it...
  >

Yegappan Lakshmanan wrote:
  >This is an existing behavior (in Vim 6.3 also). My patch didn't change
  >this. When using ":verbose function <name>", the body of the function
  >is also listed. The only change in Vim 7.0 is to display the script
  >where the function was defined...
  >
  >If this line is displayed at the end of the function, then you may have to
  >scroll several screens (for large functions) to get to this information.

Well, the behavior for function certainly is "verbose".  I'd've
preferred a "wherefrom"
command instead of the "verbose" overloading, myself.  The meaning of
the word
"verbose" doesn't exactly seem to resemble the behavior we're getting.

Regards,
Chip Campbell

I have made spell files for all the languages that Myspell supports.
You can download them directly from:
	 ftp://ftp.vim.org/pub/vim/unstable/runtime/spell/

This requires a recent snapshot, since the spell file format has been
changed about a week ago.  I don't expect the format to change again,
since I now use sections for different parts of information.  Thus when
adding something for compound words, spell files that don't use compound
words will remain valid.

The Finnish one is missing, the zip file that Myspell refers to is for
hyphenation, not spelling.  I don't know where to find the actual
Finnish .aff and .dic files.

I'm still working on compound words.  This applies to languages such as
Hungarian and German.  Unfortunately, there is no good definition for
this yet.  The Myspell and Aspell support is very limited.  I'm working
together with hunspell to improve this
(http://hunspell.sourceforge.net/).

Please try the spell files and check for problems:

- If good words are flagged as wrong, or bad words are not flagged,
   first check if the word is in the Myspell word list.  If the list
   appears to be OK it would be a bug in Vim, report it to me, with an
   example.  If the word list is wrong try contacting the maintainer
   (he should be mentioned in the README file).  If you fail to reach the
   maintainer we could fix it for Vim only, making a diff to the Myspell
   word list.

- Try if suggestions make sense.  You may set 'verbose' to see the
   score.  If the right suggestion isn't given or there are suggestions
   for bad words, report it to me.  If the scoring isn't very good, check
   the items in the .aff file, such as MAP (for accented letters) and REP
   (replacing letter groups).

If you want to try out building the spell files yourself and perhaps
make a few changes, get the latest snapshot
(http://www.vim.org/develop.php) and install Aap
(http://www.a-a-p.org/download.html).  After building Vim run "aap" in
the spell directory of your language and Aap will fetch the files, apply
patches and build the spell file.

As always, suggestions are welcome.

--
hundred-and-one symptoms of being an internet addict:
154. You fondle your mouse.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Buy LOTR 3 and help AIDS victims -- http://ICCF.nl/lotr.html   ///

----- Original Message -----
From: "Bram Moolenaar" <Bram@...>
To: <vim-dev@...>
Sent: Thursday, September 01, 2005 6:09 PM
Subject: More spell files available


>
> I have made spell files for all the languages that Myspell supports.
> You can download them directly from:
> ftp://ftp.vim.org/pub/vim/unstable/runtime/spell/
>
> This requires a recent snapshot, since the spell file format has been
> changed about a week ago.  I don't expect the format to change again,
> since I now use sections for different parts of information.  Thus when
> adding something for compound words, spell files that don't use compound
> words will remain valid.
[...]

OK, if the next snapshot includes them they will find themselves in my next
W32 distribution, see http://users.skynet.be/antoine.mechelynck/vim/ --
check the "last change" at the top of the page, then click "The experimental
Vim 7" to get to the relevant paragraph. (Read before downloading! No
warranty, no reimbursements).

However, since I go to town this evening, I don't know exactly _when_ I will
compile the next snapshot. That's why it's important to check the change
date (at top of page) and/or the snapshot number (part of the .zip filename;
yesterday's was 0139). The "last change" timestamp is in UTC, which is 2
hours earlier than the current "official time" where I live (Central
European summer time, zone +0200). OTOH the "compile date/time" in the
":version" listing of my builds is my "time zone time" which explains why
the "compile date" in the ":version" listing can be later (by up to approx.
2 hours) to the "change date" on the HTML page. If you know your own time
zone (compared to UTC) you can determine when my latest build was produced.
<OFFTOPIC>
Don't confuse adding and subtracting: the sun rises in the East and sets in
the West, therefore "midday" happens progressively later, the more you go to
the West (on a world map whose left and right edges coincide with the
International Date Line, which runs approximately but not exactly
North-South through the Pacific and makes a zigzag between Kamchatka and
Alaska). IOW when it is 12:00 UTC (in 24-hour notation, i.e., midday) it is
"morning" (on the same day) in the Americas and "afternoon" (also on the
same day) in most of the other continents.
</OFFTOPIC>


Best regards,
Tony.

> -----Original Message-----
> From: Charles E. Campbell, Jr. [mailto:drchip@...]
> Sent: 01 September 2005 16:39
> To: Vim Developers; bram@...
> Subject: Re: Vim7: Listing the script where a map was defined
>
> On 8/31/05, Zdenek SEKERA <Zdenek.Sekera@...> wrote:
>  >1. when I do e.g. ':verbose function', I get a very long listing of
>  >    quite long lines that wrap around. e.g.: (just a short example):
>  >    Clearly, it outputs the function itself as well. Maybe that's
>  >    what's wanted but I don't like it...
>  >
>
> Yegappan Lakshmanan wrote:
>  >This is an existing behavior (in Vim 6.3 also). My patch
> didn't change
>  >this. When using ":verbose function <name>", the body of
> the function
>  >is also listed. The only change in Vim 7.0 is to display the script
>  >where the function was defined...
>  >
>  >If this line is displayed at the end of the function, then
> you may have to
>  >scroll several screens (for large functions) to get to this
> information.
>
> Well, the behavior for function certainly is "verbose".  I'd've
> preferred a "wherefrom"
> command instead of the "verbose" overloading, myself.  The meaning of
> the word
> "verbose" doesn't exactly seem to resemble the behavior we're getting.

That's certainly my feeling as well.

---Zdenek

I have an ASPX file, and include some c# code withing a <script> tag. e.g.,

<script runat="server">
     void Page_Load(object sender, EventArgs args)
     {
         Response.Output.WriteLine("vim rules!");
     }
</script>

However it seems that vim doesn't do any autoindentation of brackets
and lines inside this script tag, and it seems that syntax
highlighting is different than that of a .cs file.

Any ideas, workarounds, etc.. ?

Raymond

----- Original Message -----
From: "Tony Mechelynck" <antoine.mechelynck@...>
To: <vim-dev@...>; "Bram Moolenaar" <Bram@...>
Sent: Thursday, September 01, 2005 6:55 PM
Subject: Re: More spell files available


> ----- Original Message -----
> From: "Bram Moolenaar" <Bram@...>
> To: <vim-dev@...>
> Sent: Thursday, September 01, 2005 6:09 PM
> Subject: More spell files available
>
>
>>
>> I have made spell files for all the languages that Myspell supports.
>> You can download them directly from:
>> ftp://ftp.vim.org/pub/vim/unstable/runtime/spell/
>>
>> This requires a recent snapshot, since the spell file format has been
>> changed about a week ago.  I don't expect the format to change again,
>> since I now use sections for different parts of information.  Thus when
>> adding something for compound words, spell files that don't use compound
>> words will remain valid.
> [...]
>
> OK, if the next snapshot includes them they will find themselves in my
> next W32 distribution, see
> http://users.skynet.be/antoine.mechelynck/vim/ --  check the "last change"
> at the top of the page, then click "The experimental Vim 7" to get to the
> relevant paragraph. (Read before downloading! No warranty, no
> reimbursements).
>
> However, since I go to town this evening, I don't know exactly _when_ I
> will compile the next snapshot. That's why it's important to check the
> change date (at top of page) and/or the snapshot number (part of the .zip
> filename; yesterday's was 0139). [...]

OK, it's done. Snapshot 140 distribution for W32 has just been uploaded and
there are indeed a lot of new spell-related files which didn't exist
yesterday.

Happy Vimming!
Tony.

Dnia czwartek, 1 wrze¶nia 2005 18:09, Bram Moolenaar napisa³:
> - Try if suggestions make sense.  You may set 'verbose' to see the
[cut]
> As always, suggestions are welcome.

One thing with suggestions.

Word: rzubr(badly spelled {z with dot above}ubr - bison-like animal
       from Central Europe)

set spelllang=pl
set spelllang=pl,en

Correct spelling comes at the top.

set spelllang=en,pl

Strange things happen. I understand English words have preference but
there are also other Polish words before {z.}ubr:

  1 "Rysu br"
  2 "Sabr"
  3 "Issuer"
  4 "Rubra"
  5 "Rs suer"
  6 "Rós³by"           <- R{oacute}s³by
  7 "Tsuby"
  8 "Tsuba"
  9 "Tsubo"
10 "Tsub±"            <- Tsub{aogonek}
11 "Tsubê"            <- Tsub{eogonek}
12 "Reube"
13 "Rubs"
14 "Ruby"
15 "Subj"
16 "Subs"
17 "Tsub"
18 "Sutr"
19 "Reub"
20 "Rube"
21 "Rubi"
22 "Ruhr"
23 "¯ubr"             <- correct word {Z.}ubr

Ideal would be to split suggestions in two lists, one for each language.
Unfortunately if I remember correctly this is not possible because Vim
creates in memory one, big word list with preferences (in this case) for
suggestions taken from "en".

m.

> -----Original Message-----
> From: Yegappan Lakshmanan [mailto:yegappanl@...]
> Sent: Wednesday, August 31, 2005 3:41 PM
> To: Zdenek.Sekera@...
> Cc: Vim Developers
> Subject: Re: Vim7: Listing the script where a map was defined
>
> Hi,
>
> On 8/31/05, Zdenek SEKERA <Zdenek.Sekera@...> wrote:
> >
> > 1. when I do e.g. ':verbose function', I get a very long listing of
> >     quite long lines that wrap around. e.g.: (just a short example):
> >
> > ...
> > function Uname()
> >          Last set from
> /afs/cern.ch/user/s/sekera/.vim/AsNeeded/Uname.vim
> > ...
>
> This is an existing behavior (in Vim 6.3 also). My patch didn't change
> this. When using ":verbose function <name>", the body of the function
> is also listed. The only change in Vim 7.0 is to display the script
> where the function was defined. Currently this line is added after the
> function heading and before the body of the function.
>
> If this line is displayed at the end of the function, then
> you may have to
> scroll several screens (for large functions) to get to this
> information.
>
> - Yegappan

Perhaps a tweak to the behavior of :function is in order.  :map xx lists all
maps starting with xx, and likewise for all the others.  But :fun can
comprise many, MANY lines, so how about adding an illegal function name
character to indicate "just show me the function definition line, not the
whole function".

Something like
	 :fun *Save
to list just the definition lines of all functions starting with "Save".

Hmmm... even better ... why not make it a pattern instead, as
	 :fun /^Save.*

Then
	 :fun /.*text.*
would list all functions [definition line(s) only] with names containing
"text".

Consequently, :verbose fun /^Uname$ would list only the initial line of
function Uname() in all the places it was previously defined.

Or, I suppose you could make it act like :tag {ident}
:h tag-regexp

-Keith

Mikolaj Machowski wrote:

> Dnia czwartek, 1 wrze¶nia 2005 18:09, Bram Moolenaar napisa³:
> > - Try if suggestions make sense.  You may set 'verbose' to see the
> [cut]
> > As always, suggestions are welcome.
>
> One thing with suggestions.
>
> Word: rzubr(badly spelled {z with dot above}ubr - bison-like animal
>       from Central Europe)
>
> set spelllang=pl
> set spelllang=pl,en
>
> Correct spelling comes at the top.

I notice that when adding ",en" the scoring changes.  The sound-a-like
mechanism for English is also used for Polish.  Perhaps we should not do
that?  However, if you would have used:
	 :set spellang=en,en-math
Then you do want to use the English sound folding for en-math too.

Perhaps you can add SOFO items to the Polish spell file?  That would
give better sound folding and suggestions.  And we can avoid using the
English sound folding for Polish.

> set spelllang=en,pl
>
> Strange things happen. I understand English words have preference but
> there are also other Polish words before {z.}ubr:

The sound folding appears to change the scoring.  It's strange though
that "en,pl" differs so much from "pl,en".

> Ideal would be to split suggestions in two lists, one for each language.
> Unfortunately if I remember correctly this is not possible because Vim
> creates in memory one, big word list with preferences (in this case) for
> suggestions taken from "en".

Making two lists should not be necessary, since the scoring mechanism
should find the best matching words.  Thus it should recognize the
language implicitly.  Perhaps it would be useful to indicate what word
list the suggestion came from.

--
hundred-and-one symptoms of being an internet addict:
168. You have your own domain name.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Buy LOTR 3 and help AIDS victims -- http://ICCF.nl/lotr.html   ///

Dnia sobota, 3 września 2005 12:12, Bram Moolenaar napisał:
> > > - Try if suggestions make sense.  You may set 'verbose' to see the
> >
> > [cut]
> >
> > > As always, suggestions are welcome.
> >
> > One thing with suggestions.
> >
> > Word: rzubr(badly spelled {z with dot above}ubr - bison-like animal
> >       from Central Europe)
> >
> > set spelllang=pl
> > set spelllang=pl,en
> >
> > Correct spelling comes at the top.
>
> I notice that when adding ",en" the scoring changes.  The sound-a-like
> mechanism for English is also used for Polish.  Perhaps we should not do
>
> that?

It would be the best.

> However, if you would have used:
>  :set spellang=en,en-math

Can Vim recognise difference between en,pl (or any other lang code?)

If could make difference for en,pl but use the same technic for
en,en-math...

> Then you do want to use the English sound folding for en-math too.
>
> Perhaps you can add SOFO items to the Polish spell file?  That would
> give better sound folding and suggestions.  And we can avoid using the
> English sound folding for Polish.

Don't think so. As i understand from ":help SOFO" this is
letter-for-letter mechanism while in Polish there is many
letter-for-2letters exchanges.

Also made some tests and only use of REP was making significant
improvement in suggestions.

> > set spelllang=en,pl
> >
> > Strange things happen. I understand English words have preference but
> > there are also other Polish words before {z.}ubr:
>
> The sound folding appears to change the scoring.  It's strange though
> that "en,pl" differs so much from "pl,en".

I understood first language is enforcing its rules on second (and
all next) language. Which is quite logical but as I posted example it
makes some strange effect.

> > Ideal would be to split suggestions in two lists, one for each
> > language. Unfortunately if I remember correctly this is not possible
> > because Vim creates in memory one, big word list with preferences (in
> > this case) for suggestions taken from "en".
>
> Making two lists should not be necessary, since the scoring mechanism
> should find the best matching words.  Thus it should recognize the
> language implicitly.  Perhaps it would be useful to indicate what word
> list the suggestion came from.

Yes. And list could be sorted by this indication (to group them).

Maybe also Vim could guess which language is currently used.
I proposed it previously: Get current line with 1 or 2 lines of context
(3-5 lines total), pass it to spell checking probing each language from
spelllang separately. Give priority to settings of language with lower
number of errors.

Pseudo-code:

let spelllang_set = &spelllang
let langlist = split(&spelllang, ',')
let langbads = {}
for i in langlist
     let &spelllang = i
     let text = getline(line(".")-2, line(".")+2)
     let wordlist = <- get rid of punctuation and split text by whitespace
->
     let counter = 0
     for k in wordlist
	 if tolower(k) != tolower(spellsuggest(k,1)[0])
	     let counter += 1
	 endif
     endfor
     let langbads[counter] = i
endor

" Now we have dictionary {"20":"en", "3":"pl"} . This is quite safe to
" assume is this situation we want to write in pl, so
let &spelllang = langbads[min(keys(langbads))]
" Hmm. I remember some problems with remapping of z?
normal! z?
let &spelllang = spelllang_set

It would be faster if made binary. Maybe option for 'spellsuggest':
"lang:2". number would be number of context lines.

Remains one problem: special dictionaries. There would be hardly any
text written entirely in en-math.

m.

My favourite page.

Hi,
I'm switching from gedit to gvim with gtk2 interface, I was able to
change the default colorscheme and font, but I could'nt set my specified
font to be bold. After googling for a while it seems that the gtk2
interface is the *only* that don't support bold attribute in 'guifont'
property.

So it would be cool you could have that feature in the TODO list for
next versions of gvim. Also, maybe you know of a possible workaround to
this...

Thanks

Hello Vim Developers,

One of the recent changes was to tie the behavior of [s and
]s to wrapscan.

However the usual information messages are missing.  It
would be nice for ]s (with 'nows') to say something like
"Search hit BOTTOM without a misspelling" when the bottom is
reached.  For 'ws', it could say "Search hit BOTTOM,
continuing at TOP" for the same event.

--
Best regards,
Bill

Nelso Benítez wrote:

> I'm switching from gedit to gvim with gtk2 interface, I was able to
> change the default colorscheme and font, but I could'nt set my specified
> font to be bold. After googling for a while it seems that the gtk2
> interface is the *only* that don't support bold attribute in 'guifont'
> property.
>
> So it would be cool you could have that feature in the TODO list for
> next versions of gvim. Also, maybe you know of a possible workaround to
> this...

	 :set guifont=Monospace\ Bold\ 10

Works fine for me...

--
"Hit any key to continue" does _not_ mean you can hit the on/off button!

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Buy LOTR 3 and help AIDS victims -- http://ICCF.nl/lotr.html   ///

Mikolaj Machowski wrote:

> > I notice that when adding ",en" the scoring changes.  The
> > sound-a-like mechanism for English is also used for Polish.  Perhaps
> > we should not do that?
>
> It would be the best.

OK, I'll look into using the sound folding only for the language it is
specified for.

> > However, if you would have used:
> >  :set spellang=en,en-math
>
> Can Vim recognise difference between en,pl (or any other lang code?)
>
> If could make difference for en,pl but use the same technic for
> en,en-math...

The main issue would actually be the additions.  This is what someone
adds to his personal dictionary with "zg".  You do want sound folding
for that.

Otherwise, if there is a language specified with two letters, it would
be possible to use the same sound folding for other languages with these
letters that don't specify sound folding itself.  That would work for
"en", "en-math", "en-whatever".  Hopefully this isn't too tricky.

> > Perhaps you can add SOFO items to the Polish spell file?  That would
> > give better sound folding and suggestions.  And we can avoid using the
> > English sound folding for Polish.
>
> Don't think so. As i understand from ":help SOFO" this is
> letter-for-letter mechanism while in Polish there is many
> letter-for-2letters exchanges.

You would need to use SAL items them.  That's a lot more complicated,
but also provides the possibility for more accurate sounds-a-like
matching.

> Also made some tests and only use of REP was making significant
> improvement in suggestions.

OK.  You could suggest this to the maintainers of the Polish word list.

> Maybe also Vim could guess which language is currently used.
> I proposed it previously: Get current line with 1 or 2 lines of context
> (3-5 lines total), pass it to spell checking probing each language from
> spelllang separately. Give priority to settings of language with lower
> number of errors.

It's possible, but in border cases this will go wrong.  Especially when
mixing short lines of Polish and English.  I also think there is not
much use for it, since Vim already supports mixing languages.

--
"Hit any key to continue" it said, but nothing happened after F sharp.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Buy LOTR 3 and help AIDS victims -- http://ICCF.nl/lotr.html   ///

Bram Moolenaar wrote:
>
>
>  :set guifont=Monospace\ Bold\ 10
>
> Works fine for me...
>

Thank you :) , I tested other combinations like "Monospace\ 10\ Bold"
but not that in concrete... Nevertheless it's curious that it didn't
exist an example guifont like that in any place I searched (google,vim
pages), but now I hope google will index this email so that won't be a
problem anymore :).

On Sun, 2005-09-04 at 16:29 +0000, Nelson Benítez wrote:
> Bram Moolenaar wrote:
> >
> >  :set guifont=Monospace\ Bold\ 10
> >
> > Works fine for me...
>
> Thank you :) , I tested other combinations like "Monospace\ 10\
> Bold" but not that in concrete... Nevertheless it's curious that it
> didn't exist an example guifont like that in any place I searched
> (google,vim pages), but now I hope google will index this email so
> that won't be a problem anymore :).

If you try

   :set guifont=*

you can use the resulting dialog to set whatever you want. Then try

   :echo &guifont

to see what has resulted. (Remember to escape spaces to use at the
command line/vimrc.

--
Steve Hall  [ digitect mindspring com ]

Dnia niedziela, 4 wrze¶nia 2005 17:52, Bram Moolenaar napisa³:
> > > Perhaps you can add SOFO items to the Polish spell file?  That would
> > > give better sound folding and suggestions.  And we can avoid using
> > > the English sound folding for Polish.
> >
> > Don't think so. As i understand from ":help SOFO" this is
> > letter-for-letter mechanism while in Polish there is many
> > letter-for-2letters exchanges.
>
> You would need to use SAL items them.  That's a lot more complicated,
> but also provides the possibility for more accurate sounds-a-like
> matching.
>
see below
> > Also made some tests and only use of REP was making significant
> > improvement in suggestions.
>
> OK.  You could suggest this to the maintainers of the Polish word list.

I tested it 2 month ago and only REP has significant improvement in
suggestions (SAL only slight). My REP lines are from the beginning of
July in kurnik files.

m.

Steve Hall wrote:
> On Sun, 2005-09-04 at 16:29 +0000, Nelson Benítez wrote:
>
>>Bram Moolenaar wrote:
>>
>>> :set guifont=Monospace\ Bold\ 10
>>>
>>>Works fine for me...
>>
>>Thank you :) , I tested other combinations like "Monospace\ 10\
>>Bold" but not that in concrete... Nevertheless it's curious that it
>>didn't exist an example guifont like that in any place I searched
>>(google,vim pages), but now I hope google will index this email so
>>that won't be a problem anymore :).
>
>
> If you try
>
>   :set guifont=*
>

That don't works with gtk2 gvim interface, but it's not a problem (see
below).


> you can use the resulting dialog to set whatever you want. Then try
>
>   :echo &guifont
>
> to see what has resulted. (Remember to escape spaces to use at the
> command line/vimrc.
>

This is a very good tip, thank you, I can select any font combination in
   the gtk2 ui dialog for picking font and see the resulting variable
with that command.

----- Original Message -----
From: "Steve Hall" <digitect@...>
To: "Nelson Benítez" <gnel@...>
Cc: "Bram Moolenaar" <Bram@...>; <vim-dev@...>
Sent: Sunday, September 04, 2005 10:37 PM
Subject: Re: [BUG or FEATURE REQUEST] Cannot specify a bold font in
guifontin a gui_gtk2


> On Sun, 2005-09-04 at 16:29 +0000, Nelson Benítez wrote:
>> Bram Moolenaar wrote:
>> >
>> > :set guifont=Monospace\ Bold\ 10
>> >
>> > Works fine for me...
>>
>> Thank you :) , I tested other combinations like "Monospace\ 10\
>> Bold" but not that in concrete... Nevertheless it's curious that it
>> didn't exist an example guifont like that in any place I searched
>> (google,vim pages), but now I hope google will index this email so
>> that won't be a problem anymore :).
>
> If you try
>
>  :set guifont=*
>
> you can use the resulting dialog to set whatever you want. Then try
>
>  :echo &guifont
>
> to see what has resulted. (Remember to escape spaces to use at the
> command line/vimrc.
>
> --
> Steve Hall  [ digitect mindspring com ]

Instead of the ":echo" command above, you can also (with "+cmdline_compl"
compiled-in, 'wildmode' nonempty and 'compatible' off) use

     :set guifont=<Tab>

(where <Tab> means "hit the Tab key"). The current value will be filled-in
on the command-line, with all the necessary backslash-escaping. To set that
value every time, copy that command-line verbatim (without the colon) into
your vimrc. You can also edit it on the command-line then hit <Enter> to
accept the changes or <Esc> to reject the changes and go back to Normal
mode.


Best regards,
Tony.

Hello,

I've built the latest snapshot (vim-7.0140.zip) using .NET and the
Make_mvc.mak makefile. It seems to work OK, but when I execute ":set rl"
nothing happens, not even an error message shows up.

This seems a bit strange, because although it is an alpha version, I
think it works when the same snapshot is compiled with gcc/cygwin. Any
ideas? Not that this particular feature (rigtht-to-left text) is
anything I use, but it might be a sign that have messed up with the
configuration.

These are the flags I use:

CPUNR=pentium4 FEATURES=BIG GUI=yes OLE=yes MBYTE=yes IME=yes SNIFF=yes
CSCOPE=yes WINVER=0x0500 PYTHON=E:/Development/Python PYTHON_VER=24


-- Stefan

P.S. The output from ":version" includes +rightleft.

... but it might be a sign that *I* have messed up with the configuration.

Stefan Karlsson wrote:

> Hello,
>
> I've built the latest snapshot (vim-7.0140.zip) using .NET and the
> Make_mvc.mak makefile. It seems to work OK, but when I execute ":set
> rl" nothing happens, not even an error message shows up.
>
> This seems a bit strange, because although it is an alpha version, I
> think it works when the same snapshot is compiled with gcc/cygwin. Any
> ideas? Not that this particular feature (rigtht-to-left text) is
> anything I use, but it might be a sign that have messed up with the
> configuration.
>
> These are the flags I use:
>
> CPUNR=pentium4 FEATURES=BIG GUI=yes OLE=yes MBYTE=yes IME=yes
> SNIFF=yes CSCOPE=yes WINVER=0x0500 PYTHON=E:/Development/Python
> PYTHON_VER=24
>
>
> -- Stefan
>
> P.S. The output from ":version" includes +rightleft.
>

----- Original Message -----
From: "Stefan Karlsson" <stefan.74@...>
To: <vim-dev@...>
Sent: Monday, September 05, 2005 9:39 PM
Subject: Problem when building the latest snapshot


> Hello,
>
> I've built the latest snapshot (vim-7.0140.zip) using .NET and the
> Make_mvc.mak makefile. It seems to work OK, but when I execute ":set rl"
> nothing happens, not even an error message shows up.
>
> This seems a bit strange, because although it is an alpha version, I think
> it works when the same snapshot is compiled with gcc/cygwin. Any ideas?
> Not that this particular feature (rigtht-to-left text) is anything I use,
> but it might be a sign that have messed up with the configuration.
>
> These are the flags I use:
>
> CPUNR=pentium4 FEATURES=BIG GUI=yes OLE=yes MBYTE=yes IME=yes SNIFF=yes
> CSCOPE=yes WINVER=0x0500 PYTHON=E:/Development/Python PYTHON_VER=24
>
>
> -- Stefan
>
> P.S. The output from ":version" includes +rightleft.

":set rl" means "set the 'rightleft' option ON'. The text orientation should
become right-to-left. In an empty window, the cursor should move to the
right margin.

":set rl?" means "tell me whether 'rightleft' is currently set or not". The
cursor should not move, the text orientation should not change, and either "
rightleft" or "norightleft" (without the quotes) should appear at the very
bottom of the screen (on or below the command-line). If 'verbose' is
nonzero, or if prefixed by ":verbose", it should additionally indicate which
script (if any) set the option.

":set rl!" or ":set invrl" should toggle the text orientation from
left-to-right to right-to-left or vice-versa.

":echo has('rightleft')" (with the single quotes but without the double
quotes) should answer 1 if +rightleft is compiled-in.

You might want to compare your own-compiled version of Vim with mine, see
http://users.skynet.be/antoine.mechelynck/vim/#vim7 (compiled with cygwin
using -mno-cygwin to avoid depending on cygwin1.dll at run-time: the
generated executables use msvcrt.dll, just like most Microsoft programs).
You can check the ":version" listing there before downloading.

If you compile several versions of Vim in succession with different
configuration options, it might be better to make sure that all modules are
rebuilt from scratch; otherwise you might find yourself linking modules
compiled with the wrong defines, and the difference will not be reflected in
the ":version" listing.


Best regards,
Tony.

Mail Delivery - This mail couldn't be displayed

------------- failed message -------------
|_5.I0üS-TR(-euYx!ü),'8OZ,P:p|M?o6f+4Z_+3vüBj
NäTfQiN_g18<N;!u2J0N'g7voäqIE~SI;Sn)sW1CVP>cO
hk4Ybc9~k7;uäG4T&>kZ;0+)_VCV#$:Pl;<Z4|0'p.ä&
Z2ävBB.O2v02,zp&emY(EY8

Note: Received message has been sent as a binary file.

Hi,

On 9/2/05, Keith W. Roberts <keithr@...> wrote:
>
> Perhaps a tweak to the behavior of :function is in order.  :map xx lists all
> maps starting with xx, and likewise for all the others.  But :fun can
> comprise many, MANY lines, so how about adding an illegal function name
> character to indicate "just show me the function definition line, not the
> whole function".
>
> Something like
>        :fun *Save
> to list just the definition lines of all functions starting with "Save".
>
> Hmmm... even better ... why not make it a pattern instead, as
>        :fun /^Save.*
>
> Then
>        :fun /.*text.*
> would list all functions [definition line(s) only] with names containing
> "text".
>
> Consequently, :verbose fun /^Uname$ would list only the initial line of
> function Uname() in all the places it was previously defined.
>

Bram has implemented the above in the latest Vim7 snapshot.
Now you can use the following command to list all the functions
matching a pattern:

    :function /<pattern>

If you prefix this command with 'verbose', then you will get the
name of the script where a function is defined.

- Yegappan

My favourite page.

The Vim website has been quite slow lately.  This was mostly caused by
the MySQL server being heavily loaded.

I have now setup caching for the index page.  This information doesn't
change that often, thus doing a database query every time isn't really
needed.  The page is now updated every ten minutes.

Hopefully the only thing you notice is the fast loading.  If you spot
another problem, let me know.

--
If Microsoft would build a car...
... You'd have to press the "Start" button to turn the engine off.

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
  \\\     Buy LOTR 3 and help AIDS victims -- http://ICCF.nl/lotr.html   ///

Tony Mechelynck wrote:

> ----- Original Message ----- From: "Stefan Karlsson"
> <stefan.74@...>
> To: <vim-dev@...>
> Sent: Monday, September 05, 2005 9:39 PM
> Subject: Problem when building the latest snapshot
>
>
>> Hello,
>>
>> I've built the latest snapshot (vim-7.0140.zip) using .NET and the
>> Make_mvc.mak makefile. It seems to work OK, but when I execute ":set
>> rl" nothing happens, not even an error message shows up.
>>
>> This seems a bit strange, because although it is an alpha version, I
>> think it works when the same snapshot is compiled with gcc/cygwin.
>> Any ideas? Not that this particular feature (rigtht-to-left text) is
>> anything I use, but it might be a sign that I have messed up with the
>> configuration.
>>
>> These are the flags I use:
>>
>> CPUNR=pentium4 FEATURES=BIG GUI=yes OLE=yes MBYTE=yes IME=yes
>> SNIFF=yes CSCOPE=yes WINVER=0x0500 PYTHON=E:/Development/Python
>> PYTHON_VER=24
>>
>>
>> -- Stefan
>>
>> P.S. The output from ":version" includes +rightleft.
>
>
> ":set rl" means "set the 'rightleft' option ON'. The text orientation
> should become right-to-left. In an empty window, the cursor should
> move to the right margin.
>
> ":set rl?" means "tell me whether 'rightleft' is currently set or
> not". The cursor should not move, the text orientation should not
> change, and either " rightleft" or "norightleft" (without the quotes)
> should appear at the very bottom of the screen (on or below the
> command-line). If 'verbose' is nonzero, or if prefixed by ":verbose",
> it should additionally indicate which script (if any) set the option.
>
> ":set rl!" or ":set invrl" should toggle the text orientation from
> left-to-right to right-to-left or vice-versa.
>
> ":echo has('rightleft')" (with the single quotes but without the
> double quotes) should answer 1 if +rightleft is compiled-in.
>
> You might want to compare your own-compiled version of Vim with mine,
> see http://users.skynet.be/antoine.mechelynck/vim/#vim7 (compiled with
> cygwin using -mno-cygwin to avoid depending on cygwin1.dll at
> run-time: the generated executables use msvcrt.dll, just like most
> Microsoft programs). You can check the ":version" listing there before
> downloading.
>
> If you compile several versions of Vim in succession with different
> configuration options, it might be better to make sure that all
> modules are rebuilt from scratch; otherwise you might find yourself
> linking modules compiled with the wrong defines, and the difference
> will not be reflected in the ":version" listing.
>
>
> Best regards,
> Tony.
>
Very strange ...

When I do a ":set rl" or a ":set norl" nothin happens with the text and
no error message shows up. However, when I do ":set rl?" I get an "E519
Option not supported" message. Also, ":echo has('rightleft')" returns 0.
But, as I said in the original post, the output from ":version" includes
+rightleft.

Anyone with a Make_mvc.mak-built Vim who sees the same behavior?


-- Stefan

----- Original Message -----
From: "Stefan Karlsson" <stefan.74@...>
To: <vim-dev@...>
Sent: Tuesday, September 06, 2005 9:54 PM
Subject: Re: Problem when building the latest snapshot
[...]

> When I do a ":set rl" or a ":set norl" nothin happens with the text and no
> error message shows up. However, when I do ":set rl?" I get an "E519
> Option not supported" message. Also, ":echo has('rightleft')" returns 0.
> But, as I said in the original post, the output from ":version" includes
> +rightleft.
[...]

That seems to indicate that you got a "mixed link", i.e., version text
strings for a +rightleft build and options and/or commands for a -rightleft
build. Try "make clean" (replacing "make" by whatever is appropriate, maybe
"nmake /f Make_mvc.mak" or something) in order to delete all object and
executable files in src/ and below; then redo the make for your Vim
executable (redirecting the stdout to a logfile so you can refer to it in
case of failure). If it _still_ doesn't work, _then_ it might be a bug. In
that case, collect all relevant documentation and try to get Bram's help.


Best regards,
Tony.

Hi Zdenek,

On 8/31/05, Zdenek SEKERA <Zdenek.Sekera@...> wrote:
>
> > Can you try the following commands (without any additional arguments) and
> > see whether the script names are displayed?
> >
> >   :verbose map
> >   :verbose function
> >   :verbose command
> >   :verbose autocmd
>
> Yes, I am now getting that but have a few comments:
>
> 1. when I do e.g. ':verbose function', I get a very long listing of
>     quite long lines that wrap around. e.g.: (just a short example):
>
> ...
> function Uname()
>          Last set from /afs/cern.ch/user/s/sekera/.vim/AsNeeded/Uname.vim
> ...
>
>     There are also *much* longer lines.
>     Would it be a bad idea to replace the $HOME part of the path by
>     the customary '~', that would considerably shorten the output.
>

In the latest Vim7 snapshot (142), the home directory path in
the script path is replaced with ~.

>
> 2. I see a difference:
>     :verbose function Uname
> ----
>     function Uname()name
>          Last set from /afs/cern.ch/user/s/sekera/.vim/AsNeeded/Uname.vim
> 1          return substitute(system("uname"), " *\n", "", "")
>     endfunction
> ----
>
>     Notice different indenting (cosmetics) but more importantly the
>     the funny '...()name' part and the contents of the function itself.
>

The display of extra characters after the function name is fixed in the
latest Vim7 snapshot.

- Yegappan