Hello Bram
doc/options.txt
*'regexpengine''* *'re'*
^
also:
doc/options.txt
- *'undofile'* *'udf'*
+ *'undofile'* *'noundofile'* *'udf'* *'noudf'*
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18
Hello
-- snip --
I notice it doesn't get recognized, becaues the pattern for the filetype
is */etc/dnsmasq.conf. I think it will be ok to just match
dnsmasq.conf.
No dnsmasq.conf will get you false positives.
# find /etc -iname 'dnsmasq.conf'
/etc/dbus-1/system.d/dnsmasq.conf
Resending to list, too.
Hello Bram,
Excerpt from Bram Moolenaar:
-- snip --
I notice it doesn't get recognized, becaues the pattern for the filetype
is */etc/dnsmasq.conf. I think it will be ok to just match
dnsmasq.conf.
No dnsmasq.conf will get you false positives.
# find /etc -iname
Hello
attached is a example file for ft=dnsmasq.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
Hello Bram,
hello folks, (cc'ing vim dev)
if this already has been discussed excuse me.
Some time ago we had a discussion about how to handle specific settings in Vim
the correct way.
Now some time later i think i have a approach that could be of some use in this
regard.
example code follows:
Hello
Excerpt from Hisashi T Fujinaka:
Yep it is not showing up yet, but it will come eventually :p
Thanks for nothing, but I mentioned this because it's usually up before
the emails arrive.
Mercurial log:
Changeset:
3660 (bdf7f3e4c763) updated for version 7.3.590
Date:
2012-07-06
Hello Taro,
Excerpt from MURAOKA Taro:
-- snip --
I have updated files which I had provided.
Please check attachement and include into vim distribution.
Changes are:
* Update translations
- src/po/ja.po
- src/po/ja.sjis.po
* Add license notice (of course under VIM license)
-
Hello
-- snip --
multi-line strings should have a line ending like '\n'
in 'src/po/ja.po' there are multi-line strings e.g. line 3087 that are missing
the '\n'.
OK drop that since it is nonsense. But i wonder if '$PATH' will be replaced with
some real path. In that case it might worthwhile to
Hello
just for the record: I reviewed all changes made to runtimefiles in 'changeset:
3557:9cb3a75a20b9' and TTBOMK all are fine.
Only 'runtime/syntax/cmake.vim' still uses a non Vim License. Maintainer cc'ed.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B
Hello Bram,
Hello Folks,
Bram i am curretly working on using and extending the script snippet you
provided to check runtimefiles.
I just started and allready found e.g.:
runtime/autoload/ada.vim: Vim(function):E122: Function ada#Word already exists,
add ! to replace it in
Hello
Excerpt from Thilo Six:
-- snip --
lets have some proper english:
- Now this script runs a single inside Vim instance.
+ Now this script runs inside a single Vim instance.
-- snip --
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received
Hello Bram,
Hello Folks,
-- snip --
What i think about is to have the following:
* start vim with $ vim -i NONE -u NONE
* dump its ist whole configuration (including variables) into a file
* source a runtimefile at a time
* dump the configuration again
* diff the two configurations for
Hello Антон and Ron,
Excerpt from Антон Кочков:
Hello!
I've updated fasm vim syntax file to match fasm-1.70.02 (latest
stable) version syntax and support 64bit, MMX, SSE1-SSE4, AVX-AVX2
instructions.
Hope it can be useful.
Looking at Антонs changes i found the following:
1) Why did you
Hello Tony and Ben,
Excerpt from Ben Fritz:
-- snip --
The Vim license goes far back in the history of Vim, and I think Bram
put a lot of thought (over time) into making it exactly what he wanted.
OTOH the GPL is one of a short list of popular licenses and there may
have been requests to
Hello Tony,
Excerpt from Tony Mechelynck:
-- snip --
The Vim license goes far back in the history of Vim, and I think Bram
put a lot of thought (over time) into making it exactly what he wanted.
OTOH the GPL is one of a short list of popular licenses and there may
have been requests to
Hello
email bounced.
this patch adds 'b:undo_ftplugin' to 'runtime/ftplugin/art.vim'
d...@gte.com:
Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/I'm_not_going_to_try_again;_this_message_has_been_in_the_queue_too_long./
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C
Hello Bram,
Excerpt from Bram Moolenaar:
-- snip --
Attached patches add @Spell to the the syntax files
runtime/syntax/{bc,cmake,expect,mmix,spice,vhdl,xpm2}.
I tried to contact the maintainers but their emails
bounce for all those 7 syntax files.
I'll wait a few days, if nobody objects
Hello Gary,
Excerpt from Gary Johnson:
-- snip --
Would you be willing to set up a repository for us?
I'd be willing if I knew how, but I've never done that.
My expertise in this filed isn't large either. But thanks for helping anyway.
Regards,
Gary
--
Regards,
Thilo
Hello Ben and John,
Excerpt from Ben Fritz:
-- snip --
The files in 'runtime' would NOT be part of the group repo, but
all files in each listed directory (and subdirectories) would be
part of the group repo.
runtime (group)
+--autoload
+--colors
+--compiler
+--ftplugin
Hello Charles,
Excerpt from Charles Campbell:
-- snip --
Perhaps there could be an automated annual email such as:
---
Hello!
Thank you for your maintaining of runtimefile.vim. The Vim community
greatly appreciates your work.
This is an automated annual
Hello John,
Excerpt from John Beckett:
I am all with you here. I just want to add a note. see below.
Here are some thoughts for a group-managed repo.
It must be simple for the group managers, and for file
maintainers, and for Bram. It must also be simple for anyone to
report a problem or
Hello Bram,
Excerpt from Bram Moolenaar:
-- snip --
No objection here but a question. There are allready some more email adresses
that bounced.
I am in favour of changing the email address to vim-dev. The current
noted email address is broken anyway and therefore useless. If those
Hello Gary,
Excerpt from Gary Johnson:
On 2012-05-17, Thilo Six wrote:
I would require that we gain at least 7 individuals with commit access.
This is to somewhat grant that always someone is around who can do the job.
Anyone who is interested to volunteer for this please speak up now
Hello Ben,
Excerpt from Ben Fritz:
-- snip --
As a maintainer of a few runtime files, I have something to
make sure of: Are there any changes for the current
maintainers in what they observe--policy, obligations, or
something similar to those, to maintain the runtime files
they are in
Hello Dr. chip,
Excerpt from Charles E Campbell Jr:
-- snip --
Hello!
I've been on vacation this week, attending my daughter's graduation from
Emory University.
Congratulations.
I have several concerns about this proposal:
* vim.vim : there's a large block of code that I generate
Hello Ben,
Excerpt from Ben Fritz:
-- snip --
I would require that we gain at least 7 individuals with commit access.
This is to somewhat grant that always someone is around who can do the
job.
Anyone who is interested to volunteer for this please speak up now.
I am interested.
I am
Hello Bram,
Excerpt from Bram Moolenaar:
-- snip --
please find attached updates for:
runtime/syntax/dirpager.vim
runtime/syntax/dnsmasq.vim
runtime/syntax/gnash.vim
Thanks. I'll include them.
I prefer to keep decorations to a minimum. Keep in mind that the
files are interpreted,
Hello Karthik,
this patch adds 'b:undo_indent' to 'runtime/indent/cmake.vim'.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
Hello Nikolai,
this patch adds 'b:undo_indent' to 'runtime/indent/css.vim'.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For
Hello Jocelyn,
this patch adds 'b:undo_indent' to 'runtime/indent/eiffel.vim'.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
hello Bram,
this patch adds 'b:undo_indent' to 'runtime/indent/vim.vim'.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
Hello Ernie,
Excerpt from Ernie Rael:
-- snip --
By other mail it looks like the big procedural issue of repository
hierarchy/operation is getting close to agreement.
-- snip --
I might not have been explicit enough about this yet. So lets fix that. I wont
create those repos and i do not
Hello Dominique,
Excerpt from Dominique Pellé:
John Beckett johnb.beck...@gmail.com wrote:
Kazunobu Kuriyama wrote:
As a maintainer of a few runtime files, I have something to
make sure of: Are there any changes for the current
maintainers in what they observe--policy, obligations, or
Hello Kazunobu and John,
Excerpt from John Beckett:
Kazunobu Kuriyama wrote:
As a maintainer of a few runtime files, I have something to
make sure of: Are there any changes for the current
maintainers in what they observe--policy, obligations, or
something similar to those, to maintain the
Hello Bram,
i have a question regarding 'runtime/ftplugin/zimbu.vim'.
I see 'b:undo_ftplugin' undoes somes things. But isn't
'efm tw et sts sw' missing?
What about functions? Shouldn't we 'delf' them, too?
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
Hello Bram,
'runtime/indent/zimbu.vim' uses line-continuation without cpo handling. This
patch adds that. Though i am not exactly sure i did it right. Line-continuation
happens inside a function with several 'return's surrounding. Please review.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0
Hello Bram,
-- snip --
'runtime/indent/zimbu.vim' uses line-continuation without cpo handling. This
patch adds that. Though i am not exactly sure i did it right.
Line-continuation
happens inside a function with several 'return's surrounding. Please review.
Additionally i think
Hello Tim,
looking at 'runtime/indent/liquid.vim' i notice it does not make use of
'b:undo_indent' though it sets 'indentexpr' and 'indentkeys' to nonstandard
values.
I am most probably wrong on the following so please review:
'runtime/indent/liquid.vim' uses '[^\n]' though it does not handle
Hello Philip,
i noticed by looking at 'runtime/syntax/cl.vim' that it could make use of
'@Spell' so that Vim highlights spelling mistakes in comments only when editing
a cl file with those settings:
:syntax on
:set spell
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4
Hello Nicolas,
here is small patch for 'runtime/syntax/ninja.vim' so that Vim highlights
spelling mistakes in comments only when editing a file with those settings:
:syntax on
:set spell
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received
Hello Philip,
here is small patch for 'runtime/syntax/progress.vim' so that Vim highlights
spelling mistakes in comments only when editing a file with those settings:
:syntax on
:set spell
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You
Hello David,
'runtime/syntax/resolv.vim' uses '[-0-9A-Za-z_\.]' therefore it should handle
cpoptions correctly. see ':h cpo-l' for details.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not
Hello Bram,
please find attached updates for:
runtime/syntax/dirpager.vim
runtime/syntax/dnsmasq.vim
runtime/syntax/gnash.vim
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type
Hello Dorai,
this patch adds 'b:undo_ftplugin' to 'runtime/ftplugin/art.vim'
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For
Hello Johannes,
this patch adds 'b:undo_ftplugin' to 'runtime/ftplugin/cs.vim'.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
Hello Johannes,
this patch adds 'b:undo_ftplugin' to 'runtime/ftplugin/ishd.vim'.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
Hello Mario,
this patch fixes a typo inside 'b:undo_ftplugin'.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
Hello David,
this patch completes 'b:undo_ftplugin' in 'runtime/ftplugin/sql.vim'.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
Hello Bram,
Excerpt from Bram Moolenaar:
-- snip --
Including patches for runtime files doesn't take much of my time, under
the condition that I can include them as-is. Most time goes into
reviewing the change and making sure it doesn't break anything. Or
omits another change that was
Hello Bram and Ben,
Excerpt from Bram Moolenaar:
-- snip --
Including patches for runtime files doesn't take much of my time, under
the condition that I can include them as-is. Most time goes into
reviewing the change and making sure it doesn't break anything. Or
omits another change that
Hello Ernie,
Excerpt from Ernie Rael:
-- snip --
But since
there is hopefully a main guy for each file, shouldn't random changes be
kept to a minimum?
Well i can only speak for myself. Usually i very hardly try to be friendly. That
means the workflow of asking the maintainer for a change
Hi Thomas and Ben,
Excerpt from Ben Fritz:
On Wednesday, May 16, 2012 1:14:00 AM UTC-5, Thomas Köhler wrote:
OK, now things are clearer for me. That's basically a good idea,
but:
- URL would also need to change:
to Bram alone.
So basically the only change for now would then be this line:
Maintainer: Thilo Six T Dot Six At gmx dot de
would change to
Maintainer: Thilo Six vimruntime-maintainers at foo dot org
Still i am the main-maintainer but not the only one. Questions, fixes, additions
would
Hello Gary and Christian,
Excerpt from Christian Brabandt:
On Di, 15 Mai 2012, Gary Johnson wrote:
I like it.
Do you think there would be enough maintenance traffic to justify a
separate runtime-maintainers list or would vim-dev suffice?
+1
If the traffic isn't too big, I would
.
IIRC a maintainer has committed himself to be reachable via email 3 years after
his last change. (I must have read that in vim help somewhere, but need to seek
that out again first where exactly that was).
...but
$ recgrep -c by Thilo Six . | grepinvert 0$ | wc -l
28
basically all of those files
-- snip --
IIRC a maintainer has committed himself to be reachable via email 3 years
after
his last change. (I must have read that in vim help somewhere, but need to
seek
that out again first where exactly that was).
This is a good read:
:h develop.txt
though it does no contain that
Hello Dominique,
Excerpt from Dominique Pellé:
-- snip --
Some statistics: I've contacted the maintainers of 15 syntax files
this weekend to add spelling checker support. The stats so far are:
- 4 responses received from maintainers of awk, forth, ocaml, scheme
(thanks!);
- 6 emails
Hello Thomas,
I answer on list.
Excerpt from Thomas Köhler:
-- snip --
And it would help people like me that used to maintain some
runtime files in the past and now are stuck maintaining something
they don't use any longer.
I think that is exactly the meaning of team maintenance.
I commit
Hello John,
Excerpt from John Beckett:
Dominique Pellé wrote:
Yes. Maintainers were in CC of the emails. But perhaps I
should write to the maintainers only to avoid sending too many
emails to vim_dev (still more of those simple patches to
come...)
There is no good way to do this except
Hello Dominique,
Excerpt from Dominique Pellé:
Hi
Attached patch adds @Spell to the runtime/syntax/cmake.vim file
so that Vim only highlights spelling mistakes in comments when
editing a CMakeFile with those settings:
:syntax on
:set spell
There are still several syntax files
Hello Johannes,
hello Bram,
hello James,
i am looking through the list of patches which have been currently only been
made available for user of the GNU/Linux Debian distribution.
I think it would make sense to include them upstream to make them available to
all Vim users.
Bram since i had
Hello Johannes,
hello Bram,
hello James,
here is an other Debian only patch. This time for
'runtime/syntax/xdefaults.vim' you can view it at:
http://patch-tracker.debian.org/patch/series/view/vim/2:7.3.429-2/upstream/xdefaults-syntax-define.patch
or download it at:
Hello David,
the Vim runtimefiles 'runtime/doc/vimtutor-fr.1' and
'runtime/doc/vimtutor-fr.UTF-8.1' have patches available in Debian GNU/Linux
which are not yet incooperated upstream.
You can view the patches in question here:
Hello Omar,
in the Debian GNU/Linux distribution vim contains a pacth not yet inclueded
upstream. This patch is for 'src/po/es.po' and is supposed to fix 'Correct
Spanish translation for swap file recovery'.
You can review tha patch at:
Hello Tomáš,
I forward the following mail i received from Andy:
Excerpt from Andy Lester:
I don't have the original author on the cc:.
Can you please point him to https://github.com/petdance/vim-perl/issues ?
sure ;)
Thanks,
xoa
--
Andy Lester = a...@petdance.com = www.petdance.com =
Hello Tomáš,
Excerpt from Tomáš Janoušek:
Hello,
it's quite common to use the syntax Some::Package-new to create new
instances
in Perl, but using gf tries to open a file named Some/Package-.pm, which
fails. Hence, I suggest adding this to ftplugin/perl.vim:
setlocal isfname-=-
I
Hello Bram,
the hg changeset: 3492 (3482d151136b) 'Updated runtime files' has introduced
linecontinuation to 'runtime/ftplugin/dosbatch.vim'. Therefor cpo handling needs
to be added, too.
In 'runtime/ftplugin/postscr.vim' also linecontinuation has been added after the
already present cpo
Hello
Excerpt from Ingo Karkat:
On 31-Mar-2012 04:09, Bovy, Stephen wrote:
The High-Lighted Cursor Line (?? Could ??) over-lay the
intersection of the High-Lighted Number-Line :)
While it would be possible in the high-color GVIM to mix the colors of the
LineNr and CursorLine
Hello Charles,
Excerpt from Charles Campbell:
Ivan Krasilnikov wrote:
I've found that vim syntax file (runtime/syntax/vim.vim) doesn't know
about some options of :command -complete=.
For example, it highlights color in the line below as an error:
command -nargs=1 -complete=color ...
Hello Charles,
Excerpt from Charles Campbell:
-- snip --
I agree - v7.3-15 is now released with this fixed.
Thanks.
Regards,
Chip Campbell
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Hello Bram,
hello Charles,
dear Readers,
for some time now i tried to tackle a bug in highlighting of vim files. Namely
the highlighting of 'vimVar's with and without scope prefixed.
Look at the attached sample.vim with default highlighting for vim files to see
what i mean. I tried to find a
Hello Tony,
Excerpt from Tony Mechelynck:
This should work:
,[ .hgignore ]--
# use glob syntax
syntax: glob
tags
`-
-- snip --
Yes, it is possible (I do it), BUT: not only do I get a prompt whenever
I try to
Hello skeept,
Excerpt from skeept:
Hi,
I would like to know if it is possible to include
runtime/doc/tags in .hgignore?
This should work:
,[ .hgignore ]--
# use glob syntax
syntax: glob
tags
`-
-- snip --
Thanks.
Hello Marcin,
Excerpt from Marcin Szamotulski:
-- snip --
By the way: I can do 'vim -y' in the terminal and get terminal vim in easy
mode (my vim is compiled without gui - this is how vim is compiled on Gentoo,
gvim is compiled separately) and indeed I cannot save/quit.
C-l:quit
HTH
Hello İsmail,
Excerpt from İsmail Dönmez:
Hi;
using vim 7.3 patchlevel 382.
How to reproduce:
1. visudo -f /etc/sudoers
2. Write %user1 see its highlighted
3. Add a 1 so it becomes %users1 it becomes unhighlighted
I checked the SUSv3 spec and there is nothing preventing group
Hello
Excerpt from Jürgen Krämer:
-- snip --
It's in the todo list. That list is very long, and bug fixes have
priority. Might take a while.
How long is that list? It's been more than 6 months now :/
:help todo
Which might be out of date. The latest version is always available at:
Hello,
Excerpt from François Ingelrest:
-- snip --
I personally don't care whether vim.org works without the www prefix
or not, but I'd vote to fix it just to stop the recurring requests
for making it work. And I must say I can't see any reason to prevent
vim.org from working without the
Tom Ryder wrote the following on 23.02.2012 11:18
I would be interested in helping out for known problems in other
syntax files; I've been wanting to contribute to Vim for quite a
while.
That would be appreciated. There are quite a number runtimefiles which use
linecontinuation but are known
Bram Moolenaar wrote the following on 22.02.2012 17:03
Hello
Can we adjust the header to remove:
Modified By: Thilo Six
Originally: 2009-07-09
Now that you, as the maintainer, sent a new version I don't think we
need these.
/me thinks so, too.
--
Regards,
Thilo
4096R
Hello
,[ :h syn-pattern ]-
Syntax patterns are always interpreted like the 'magic' option is set,
no matter what the actual value of 'magic' is. And the patterns are
interpreted like the 'l' flag is not included in 'cpoptions'. This
was done to make syntax files
Thilo Six wrote the following on 03.02.2012 17:37
Hello Bram,
hello Maintainers,
for those who do not know MPF stands for mass patch filling. ;)
All proposed patches have been sent out to maintainers. The according list is
attached.
By the way how long should we wait on maintainers before
Andy Wokula wrote the following on 07.02.2012 20:40
-- snip --
,[ :h syn-pattern ]-
Syntax patterns are always interpreted like the 'magic' option is set,
no matter what the actual value of 'magic' is. And the patterns are
interpreted like the 'l' flag is not
Ricardo Catalinas Jiménez wrote the following on 05.02.2012 23:15
Hello Ricardo,
-- snip --
Finally Csaba and me decided to send you for inclusion in the official
Vim distribution just the ftplugin for Erlang with the modifications
that Csaba proposed.
I have updated the already sent out
Hello Bram,
hello maintainers,
regarding the license of runtimefiles the current state is as attached.
James-San already contacted me so i expect the Debian related files will be
handled.
Somewhat of a blocker currently is VisVim and 'src/sha256.c'. What to do about
them?
How long to wait on
Hello Bram,
hello Maintainers,
for those who do not know MPF stands for mass patch filling. ;)
All proposed patches have been sent out to maintainers. The according list is
attached.
By the way how long should we wait on maintainers before we consider them MIA?
Some patches sent out 2 months ago
mattn wrote the following on 24.01.2012 02:49
-- snip --
I do relicense for followings files under the terms of the Vim license.
runtime/tutor/tutor.ja.euc (converted from utf-8)
runtime/tutor/tutor.ja.sjis (converted from utf-8)
runtime/tutor/tutor.ja.utf-8
runtime/colors/shine.vim
If
Benjamin R. Haskell wrote the following on 15.01.2012 01:54
-- snip --
But, according to comments in the files, there are already files being
distributed with Vim that are GPLv2-licensed (and not Vim/GPL
dual-licensed, AFAICT):
Under runtime/:
runtime/ftplugin/logcheck.vim
Bram Moolenaar wrote the following on 15.01.2012 16:42
Thilo Six wrote:
Thilo Six wrote the following on 15.01.2012 14:12
Benjamin R. Haskell wrote the following on 15.01.2012 01:54
-- snip --
But, according to comments in the files, there are already files being
distributed with Vim
/wine-extension-vim
--- jam.vim.orig 2011-11-30 20:48:28.0 +
+++ jam.vim 2012-01-08 22:08:37.0 +
@@ -1,7 +1,7 @@
Vim syntax file
Language: JAM
Maintainer: Ralf Lemke (ralfl...@t-online.de)
- Last change: 09-10-2000
+ Last change: 2012 Jan 08 by Thilo Six
For version 5
Taylor Hedberg wrote the following on 25.12.2011 05:20
Hello Charles,
Charles E Campbell Jr, Sat 2011-12-24 @ 22:11:31-0500:
If I may repeat myself, what advantage does
set cpo-=a cpo-=A
have over
set cpo-=aA
???
From `:help :set-=`:
When the option is a
just an status update.
--
Regards,
Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
Matthew Brett wrote the following on 23.12.2011 03:25
Hello Matthew,
Hello,
I hope this is the right place to post.
I noticed this behavior in the current runtime/indent/rst.vim
test.rst
1. Sometimes I find that I write long sentences without having any idea when
they will finish
Matthew Brett wrote the following on 23.12.2011 11:51
Hello Matthew,
-- snip --
Thanks - I have done that. As a matter of interest, did I miss a
developer howto with etiquette for patches and so on? I had a quick
look but I am jet-lagged and not at my sparkling best at the moment.
No
Thilo Six wrote the following on 23.10.2011 21:37
-- snip --
Full list now attached. Danek please tell me which of those are already has
been
handled by you. Thanks.
I did a QA rescan of runtimefiles and revealed some more with a faulty
handling
of cpo settings. I consider
Thilo Six wrote the following on 15.11.2011 18:37
Hello all,
-- snip --
Thank you for the detailed analysis and the patch. I assume that your
foundings
are also related to an issue that i had myself recently without being able to
come to any useful solution.
http://thread.gmane.org
Alexey Radkov wrote the following on 14.11.2011 20:41
Hello Alexey,
-- snip --
You will be returned to the original file, but... Now there is no
syntax highlight and ':ls' will show that there is no current buffer!
':ls!' will show that the current buffer is unloaded. Same behaviour
can be
Hello Bram and Vimmers,
-- snip --
Sourcing those files seems inefficient. Using a function under autoload
seems more appropriate. Passing a dictionary to store the values in.
That also fixes nested scripts, I don't think that would work with the
source file.
I'll happily do all the
Peter Odding wrote the following on 12.11.2011 16:25
Hello Peter,
It would also be nice if the script would either 'unlet' the variables
again, or
limit their scope ':h internal-variables'. See attached patch as example.
I thought variables inside functions were implicitly in function
Hello Bram,
hello Vimmers,
just read:
Vim's 20th anniversary
http://lcorg.blogspot.com/2011/11/two-decades-of-productivity-vims-20th.html?utm_source=feedburnerutm_medium=feedutm_campaign=Feed%3A+LinuxcommandorgTipsNewsAndRants+%28LinuxCommand.org%3A+Tips%2C+News+And+Rants%29
Congratulations!
I
Tony Mechelynck wrote the following on 31.10.2011 00:08
Hello Tony,
-- snip --
vi always matches wherever vim matches, so you have a kind of
degenerate case here.
Maybe what you wanted was
/vi\%[m]
or
/vim\=
See
:help /\=
:help /\%[]
Best
1 - 100 din 156 matches
Mail list logo
