Dimitar DIMITROV wrote:
Now try :ec getpos('.') - [0, 4, 17, 0]
Move away and :call setpos('.',[0,4,17,0])
If you use up down k or j you will not move just
above/below the char but in some weird location
Say the cursor is in column 20, then setpos() is used to jump
to [d], then k is pressed.
Bram Moolenaar wrote:
I got pointed at a copyright notice in the
$VIMRUNTIME/vimlogo.eps file. That's because the file was
generated by Corel Draw and includes some stuff apparently
written by Corel.
To avoid a discussion about whether distribution is OK,
perhaps someone can take the Vim
Ben Fritz wrote:
Because my workplace's IT somehow blocks access to github and
other places when using git tools but not when using a
browser. I can download an archive from github when I point my
browser to the project webpage but git clone/fetch/pull all
fail.
You know about $http_proxy
Ben Fritz wrote:
You know about $http_proxy (or some other method of telling
the tool about your proxy server)?
Nope, never heard of such a thing. But I actually never use
git except for getting Vim plugins.
At one point I could access Hg and git repositories just fine,
but not SVN.
Sure,
lazureus wrote:
I'm encountering some similar problems as Dariusz have seen
however on the 64-bit Ubuntu. Trying to run :Rgrep from VIM
I get following error message :
Error detected while processing function
SNR19_RunGrepRecursive..SNR19_RunGrepCmd:
line 20:
E484: Can't open file
It looks like the wiki has had the answer since March 2013:
http://vim.wikia.com/wiki/Script:311
That is linked in the top line at:
http://www.vim.org/scripts/script.php?script_id=311
I have not used the plugin, but what is written at the above
looks exactly what is needed to fix the error
Lech Lorens wrote:
Would anyone else volunteer as a mentor?
For GSOC2012, Bram needed another person to register with
Google, and I was that person. I would be happy to do that again
if wanted. I could act as a coordinator to check that things are
ok for student(s) and mentor(s), and raise
It's a bit hard to see the excellent advice in that last post,
so here it is:
To delete (not cut) all lines matching pattern use:
:g/pattern/d_
John
--
--
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
Christian Brabandt wrote:
With the release of the Unicode version 7.0 yesterday, the
rouble sign has been assigned U+20BD. It probably makes sense
to update all the generated unicode data in the Vim source
however.
Can I hijack this to ask about U+2022 which is a nice bullet.
One way to
Bram Moolenaar wrote:
This is what the attached patch enables, by adding the new
flag 'N' to the 'cpo' setting.
Well, instead of adding an option, what about:
:noremap n /CR
:noremap N ?CR
The option would be much better!
I sometimes map n and N to add zz so the hit is in the
Gary Johnson wrote:
Won't that break any plugins that use 'n' or 'N' after a
reverse search?
I agree that the proposed behavior would be less confusing
than the current behavior, but changing it in any way that
would break existing scripts seems like a non-starter.
There are times when
Michael Henry wrote:
I've always been confused by the behavior of n and N
after backward searches. The only work-around my brain can
handle is to simply avoid backward searches entirely;
instead, I search forward and press N.
Agreed. That's usually how I resolve the problem as well.
Bram Moolenaar
So how about this: 7.4.000 will be released with MS-Windows
binaries that still support the old systems. Once it's out
and it looks OK we drop support for older systems. That way
7.4 is what needs to be used for old systems. It includes a
lot of bug fixes since the last
Roland Eggner wrote:
Prior to dropping support for w2k please consider:
(1) w2k is known to be the least faulty OS version released
by its vendor so far, because the phrase based on NT was a
lot more than just an advertising, the development history of
this OS version differed significantly
Bram Moolenaar wrote:
Yes, the database appears to be down.
They upgraded the project recently, but I have no reason
to assume this is related.
Please check the sourceforge site for any known problems.
Or file a support ticket.
I'm afraid I don't have time right now to look into it.
The
Bram Moolenaar wrote:
Please check the sourceforge site for any known problems.
Or file a support ticket.
I've poked around and can't find anything, so I have filed a
support ticket:
https://sourceforge.net/p/forge/site-support/3872/
John
--
--
You received this message from the vim_dev
The vim.org problem has been fixed by Sourceforge.
However, my checking of some recent changes to the vim.org
database shows that vim.org was scanned by someone with Acunetix
Web Vulnerability Scanner. That was used to generate at least
124 user accounts, including text fields intended to probe
I wanted to update our tip[1] on building Vim in Windows with
Visual Studio to use VS 2012 Express, as well as VSE2010.
While doing that I noticed that there is a double percent (%%)
in two batch files, and I'm pretty sure it is wrong. The extra
percent is ignored, so nothing bad happens, but if
Dominique Pelle wrote:
I'm wondering why I see two copies of your message.
Did it happen for just one of my email? or all of my emails?
I sent emails to vim_dev at googlegroups.com, without BCC
or CC, using gmail (web interface). If it happened for just
one email, can you precise which
Bram Moolenaar wrote:
gui_gtk_x11.c:3418: warning: not enough variable
arguments to fit a sentinel
The function definition that is in gnome-program.h looks like this:
GnomeProgram *
gnome_program_init (const char *app_id, const char *app_version,
const GnomeModuleInfo
Richard Hartmann wrote:
http://vimdoc.sourceforge.net/cgi-bin/vimfaq2html3.pl at 32.1:
-$ stty -ixon -xoff
+$ stty -ixon -ixoff
Three months ago Yegappan Lakshmanan asked me to put the FAQ on the Vim Tips
wiki. He referred me to the txt and html versions:
Tony Mechelynck wrote:
What does everyone think about making guifont unsettable from
the modeline? It is a global option, after all. I just don't
think it makes that much sense to be set from the modeline.
It is a global option, but if you know what you're doing it
may sometimes be useful
Richard Hartmann wrote:
For your own sites, you can do something like this:
This function will check if VIM finds modelines and, if
yes, will let you choose if you want to execute them.
...
Thanks. I remember seeing something similar last time this was discussed.
For anyone interested,
Milan Vancura wrote:
I'm not sure how frequent is the usage of signs today, but if
they are to be used more frequently, new functions for
handling them (and using that functions in mksession) would
be a good idea (including a possibility to clear signs in one
file/buffer). Do you agree?
Zdenek Sekera wrote:
there can be no unescaped whitespace after the '=',
(where is that in the doc)?
:help option-backslash
I'm afraid I can't help with the substance of your question, but I see that
the docs for titlestring don't say that =%! should work like it does in
statusline. For
Bram Moolenaar wrote:
Now the patch is attached, hopefully that works better.
The file diff.dat that you just attached, and your earlier inline mail are
the same. In both cases, there is a problem: the last 12 lines should be
omitted (you can see they are a slightly broken duplicate of the
Tony Mechelynck wrote:
12 extra lines at the end shouldn't be a problem, since the
patch program will ignore garbage before and after the patch proper.
I was just trying to let Bram know that it would look better if he fixed the
patch (by deleting the last 12 lines), if he were planning to
Bill McCarthy wrote:
I want +float - how do I make that happen?
One simple method is to add the following line to src/feature.h
#define FEAT_FLOAT
You could probably do that anywhere, but just after the section with #if
relating to FEAT_FLOAT is probably a good place.
I would welcome a less
Bill McCarthy wrote:
I think the correct way to pass the requested feature
without editing feature.h is:
make DEFS=-DFEAT_FLOAT
Thanks John but that didn't work here...
If you're using Make_mvc.mak, the command is:
nmake -f Make_mvc.mak DEFINES=-DFEAT_FLOAT
Looking at the make file, it
Bram Moolenaar wrote:
Here is an update for the floating point patch. The 'g' argument for
printf() was implemented and a few bug fixes.
I have compiled with this updated floating point patch under win32. Here are
some
issues you might like to address.
os_win32.h now has '#define HAVE_POW'
hermitte wrote:
I'm not sure how many people are interested in on-the-fly
compilation.
I'm not really because I program mainly in C++, and my
experience demonstrates that after the first error it is not
uncommon to have the compiler completely lost. Thus I know
this will be a very
Bram Moolenaar wrote:
Here is an update for the floating point patch.
I've done a bit more testing with the latest floating point patch. Vim's
floating
point doesn't need to cover all extremes, but the following shows some bad
results.
:help floating-point-format (in eval.txt)
It says
Bram Moolenaar wrote:
Second, the lhs and rhs of the '.' can each overflow an
integer, giving chaos.
:let a=str2float('0.3111222333')
:echo a
Result: -0.118374
How do you suggest to fix this?
I still think that using strtod() would be best, but curiosity got the better
of me
and I
Ciaran McCreesh wrote:
Probably a minor bug: doing :bufdo e turns off syntax
highlighting in hidden buffers.
for a in a.c b.c c.c ; do echo struct $a ; done vim *.c
:set hidden :silent bufdo e 2c-^
I believe this unhappy behaviour is due to the following info from ':help
bufdo':
Ian Kelling wrote:
I just wanted to say hi and introduce myself. My name is Ian
Kelling and I attend San Diego State University in
California, USA. I am very much looking forward to this
summer and very excited about contributing and getting to
know vim more intimately. Its something I
Adri Verhoef wrote:
I think there is a problem here, namely that the BOM (Byte
Order Mark, see :help 'bomb') is transferred to the shell
command, when it shouldn't. In my opinion Vim should be able
to temporarily remove the BOM, then execute the shell
command, and finally place the BOM
Yakov Lerner wrote:
cd /tmp
rm -f nosuchfile # make sure there is no such file
man 1 ls ls.txt # get some text
vimdiff -U NONE -u NONE ls.txt nosuchfile # as expected
vimdiff -U NONE -u NONE nosuchfile ls.txt # where is contents of right pane
???
On my system, the text is present in the
Bill McCarthy wrote:
My eval.c is the current release patched by both your latest
and John Beckett's fix. You new patch fails with:
vim\vimfp patch -b -p 0 -i Brams-may_not_work_with_jb.diff
patching file src/eval.c Hunk #1 FAILED at 4799.
1 out of 1 hunk FAILED -- saving rejects to file
Bram Moolenaar wrote:
Attached you will find the latest floating point patch.
Thanks Bram. I have patched and compiled without incident. A few tests, and a
superficial look at the code changes, make me believe that the new float patch
is
good. As discussed, using strtod() is much more robust.
Mikolaj Machowski wrote:
echo printf(%.0f, 0.4)
E807: expected Float argument for printf()
You mean (argument not a string):
:echo printf(%.0f, 0.4)
echo printf(%d, 4-2)
Same glitch. It's 4-2 not 4-2.
user friendly (eg. store and display 0.5 instead of 0.50)
Here is a workaround:
Bram Moolenaar wrote:
I mean: Vim is using the library printf() to do the
conversion, but I don't see a way to tell printf() to omit
superfluous zeroes.
g and G omit superfluos zeroes, as well as the decimal point:
double n = 12;
printf(%g\n, n); // prints 12
printf(%#g\n, n); //
Bram Moolenaar wrote:
g and G omit superfluos zeroes, as well as the decimal point:
double n = 12;
printf(%g\n, n); // prints 12
printf(%#g\n, n); // prints 12.
Vim is already using %g. For me the results are different.
In Vim, the code in vim_snprintf() (in message.c)
Bram Moolenaar wrote:
OK, so Borland doesn't have round() and trunc(). I rather
not have a Vim version with only part of the floating point
support. The easy solution is to disable it for Borland in
src/feature.h:
#ifdef FEAT_NORMAL
# define FEAT_EVAL
# if
Bram Moolenaar wrote:
- Added a test. Please try this, I don't know if roundoff
errors might break it.
It's a trivial issue, but test65 (floating point) disagrees with Microsoft
Visual C
MSVC 6.0.
Line 11 of test65.in is:
:$put =printf('%e', 123.456)
Corresponding result expected in
Gautam Iyer wrote:
You can wget individual patches from git.
For example:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.
git;a=commitdiff_plain;h=0deedbcc98a831284f6e9db2510e88e90e01c
286;hp=5dd06d08015cf9c0721f34f7005ecd670025c334
I use the FTP server to get patches
Dominique Pelle wrote:
Thanks for Vim-7.2a-beta, so far it looks good. I ran the
spelling checker on the help files vim7/runtime/doc/*txt of
Vim-7.2a-beta, and found a few minor typos. I attach the patch.
I just did a similar check and found a couple more (I missed several of yours!).
Put
Christian MICHON wrote:
I also track vim-dev by usually doing this: downloading the
patches, and seldom use CVS/SVN.
The biggest trouble I see is I need to format
patches/suggestions in the same way, if I do not have write
commit access.
OK but surely that comment is for another
Ben Schmidt wrote:
As a host I would suggest code google [6], as it has svn access,
an issue tracker and a wiki. A link to this project from the
official vim site, will be appropriate (with the usual warnings),
although not strictly necessary.
I too have been thinking for some time that
smu johnson wrote:
3. Perl's =cut pod comments work half the time in Vim's
syntax highlighting.
It's a compromise between performance and quality. Read:
:help :syn-sync
4. Somehow a toggle option so that when you exit out of
insert mode, it doesn't automatically move the cursor to the
Jan Minár
I'm glad to see you persist in finding more problems.
I'm sure everybody is...
In case there is any doubt, YES we are glad you are finding problems. Thanks
very
much!
I hope Bram won't mind holding back the release of 7.2 to provide a couple more
weeks for testing by you (and
Andy Wokula wrote:
Minor issue, but somehow confusing:
Unix (and DOS (Win)) users know that Vim converts some
characters when reading and writing a file:
File - Memory - Display
NL (NUL) (line break)
NUL NL NUL (^@)
With ff=mac, Vim does another conversion,
Ingo Karkat wrote:
Use :silent ! start %; the 'silent' will close the DOS
window immediately. I use this
map Leaderx :silent ! start 1 %:pCR to execute
the current file. ':p' makes this independent from the CWD,
the surrounding make it handle spaces. The 1 is the
optional title
Ben Schmidt wrote:
Justify means to insert variable-width spacing throughOUt
the entire line so the left and right margins are aligned.
That's how most books and newspaper articles appear.
And 'right justify' sometimes means this too, as it seems it
does in the Vim docs, even though it
Tony Mechelynck wrote:
Maybe you should set a config-time option (or create one) to
avoid any interaction with the shell?
Even better: If you don't want ever to become the victim of
any exploit, turn your computer off at the wall switch and
leave it off.
:-b
I haven't studied this
Robert Webb wrote:
I believe it's the same on all systems. qsort() just
compares the sign.
Of course it would be impossible to check every qsort() on all systems(), but
the
fact that strcmp() uses that logic is a pretty good sign (!) that qsort() will
as
well.
However, as others have
fnegroni wrote:
It is a feature that I would absolutely love to have: I
develop for several projects following different indentation
styles and visualisation rules.
Some code in your vimrc to detect the current directory at startup, then
implement
the wanted settings, might be easier.
Or,
Ranjeeth P T wrote:
Usually when we open an object file( in C i.e.out file ) we
get unseen characters So adding the property of objdump will be nice??
Vim is distributed with xxd. The following tip mentions the basics, then
presents a
more elablorate procedure if you need to use xxd often:
Mondal, Shishir wrote:
I have tried earlier, but could not do that: any one knows
definite steps how to unsubscribe from the list?
Please report any problem you have when you try the following (report = reply to
this mail):
Click the link in the footer of the mail:
You received this message
Vadim Zeitlin wrote:
So, for example, opening a file Аня.vcf opens the file
???.vcf on my English Windows system.
Tony's advice about encoding might fix the situation. I have the following in my
vimrc:
set encoding=utf-8
and can open a file with the name you mentioned on Windows. The font
Bram Moolenaar wrote:
Now and then I start editing a file and want to go back to a
file I edited in a previous edit session. But the name
doesn't appear in the marks or buffer list. Still, I know
the file name is in the viminfo file. There are plugins for
this, but I thought it would
Greg Warner wrote:
thanks for the feedback. I've confirmed that it's only
breaking on one of my builds, and on another it works, so I'm
sure it's just a problem with how I'm compiling it.
In the bad build, use ':version' to see what it says about Python (near the
bottom).
Perhaps that
d tbsky wrote:
after some checking, i found command like below didn't work
under vim 7:
a
1 \\
2 \\
.
It works here on Vim 7.2 as well, although I had to use help to see how.
Use ':help :a' and see what it says about Watch out for lines starting with a
backslash. The above lines work,
Mikael Jansson wrote:
I couldn't find an edit link on the Patch page.
How do I go about adding it?
The Vim Patches page is:
http://groups.google.com/group/vim_dev/web/vim-patches
As discussed in the following thread, a spammer started changing the page so it
LOOKED unchanged, but clicking a
Mikael Jansson wrote:
===
#. ECL (Embeddable Common Lisp) Interface
Author: Mikael Jansson et al
Status: Mostly complete, needs testing
Site: http://common-lisp.net/project/limp
Implements many, but not all, of the VimScript functions. See
the project page for documentation.
Richard Hartmann wrote:
Can you add the patch to the list, please? :)
Sure but I don't have time to work out what text to put.
We need something like the following from
http://groups.google.com/group/vim_dev/web/vim-patches
10. Variable tabstops
Author: Matthew Winn
Status: alpha
Following Richard's suggestion, I added a (shortened) description of Matt
Wozniski's
patch to:
http://groups.google.com/group/vim_dev/web/vim-patches
Matt: Please reply (to me or the list) if any wording needs to be changed.
John
--~--~-~--~~~---~--~~
You
Bill McCarthy wrote:
After updating my runtime today, I noted the command
`:ol[dfiles]'.
That was for an experimental patch that Bram posted:
http://groups.google.com/group/vim_dev/browse_thread/thread/20e72354ed4b2f42
I guess it will be a bit longer before the docs and the released code are
Nico Weber wrote:
If I remember correctly, you added that about a year ago
after I sent you a patch. So I guess the wiki is just outdated.
Any chance you could update the tip? I recommend deleting any info that applies
only
to older Vim (before, say, Vim 7.0, but even 7.1 if it simplifies a
Ben Schmidt wrote:
I gave up on SVN ages ago--I would have loved to use it, but
it's just too messy. Now I apply patches. Below is the script
Eventually I'd like to have a tip (http://vim.wikia.com/) on building Vim, with
probably one overview article, and separate articles for downloading,
Richard Hartmann wrote:
Can't hurt, all for it. Do you want to include the git howto
I sent to the user's list, as well? I can do it myself, just
need to know :)
Despite the fact that this thread is about the unofficial patches, I was
responding
to Ben's script that relates to the official
Matt Wozniski wrote:
For the life of me, I can't seem to get vim to recognize,
eg, xHome and Home as separate keycodes.
Perhaps the following is an explanation:
:help version7
/xHome
Previously Home and xHome could be mapped separately.
This had the disadvantage that all mappings (with
I should take a little longer checking, but in view of the potential for
damage I'm sending a preliminary opinion:
A message has just been sent to the vim_multibyte list.
Header includes:
From: b...@moolenaar.net
To: vim-multib...@vim.org
Subject: Mail Transaction Failed
Date: Thu, 18
Tom Link wrote:
Display soft-wrapped lines flushed left at the proper
indentation level if 'linebreak' is set
Author: Václav Šmilauer
I put that info, with slight changes, at:
http://groups.google.com/group/vim_dev/web/vim-patches
Please check.
John
Anycase Mike wrote:
What i want is to let the gVim supports all system fonts.For example:
:set guifont=Dungeon:h9
Any monospaced font supported by the operating system should work in
gvim. Some ideas are at:
http://vim.wikia.com/wiki/The_perfect_programming_font
I just noticed the subject of
Peter Valdemar Mørch wrote:
I'm looking for patch #15: Correctly indent wrapped lines
in particular.
Google closed the ability for groups to have web pages or files.
That is, they deleted the patches list. I had a discussion with
Bram about whether we should put the list somewhere like the
Bovy, Stephen wrote:
When I use the mouse with vim and putty on z/OS the left
mouse-click scrolls the buffer down
The term type is xterm
Please bottom post on this mailing list.
Quote a small (relevant) part of the message you are replying to,
and put your text underneath.
Delete text that
Ben Fritz wrote:
:r !dir C:\WINDOWS\system32\*.com
Volume in drive C is Local Disk
Volume Serial Number is EA9A-15F2
Directory of C:\WINDOWS\system32
02/18/2007 06:00 AM29,696 format.com
02/18/2007 06:00 AM16,384 more.com
2 File(s)
Edwin Steiner wrote:
I found it most reliable for testing to write a simple C
program that prints its argv[] array.
I did that a few years ago, and in case anyone is interested,
here is what I used.
/* Echo arguments in one line.
* John Beckett 2007/05/25
* This is to see what is passed
Robert Melton wrote:
Wow. You can not be seriously linking a two our old
executable and claiming it contains a lot of plugins.
The only thing on that github is 3 executables and a blank
README. Not to mention you have no other github activity,
at all.
Thanks Robert, you are right of course.
Bram wrote:
1. Write tests for the regexp engine, so that we can finally
use NFA.
2. Fix bugs and review patches
3. Fix bugs and review patches
2. and 3. should be able to work together, so that the mentor
(me) does not have to spend too much time on reviewing patches.
To be able to apply
Ben Schmidt wrote:
I need a backup administrator, it's mandatory for applying.
I can act as a backup if necessary, too. I've been a bit quiet
recently, but if direct questions or a direct task were in
front of me I'd be able to help out.
Thanks Ben. If Bram is not around and I have some
Charles Campbell wrote:
You may find it at:
http://www.drchip.org/
Thanks Chip. I have updated all the pages at the Vim Tips wiki
which used to refer to the old website (if anyone looks for that
in 'Recent changes'), click 'Show bots').
John
--
You received this message from the vim_dev
Marc Weber wrote:
So does anybody have an idea whether this is a (badly
written) real job offer by Bram or whether it is what it
looks like: spam?
Of course it's spam. I have already notified Bram and deleted
the original post from the Google Groups archive.
I don't think there is anything
Marc Weber wrote:
It does not talk about the kind of employee they are looking
for (coder, artist, ..)
I had better warn any naive readers:
Never believe anything you read on the Internet, including
emails that appear to come from Bram.
Spam can be spam (it is genuinely promoting something).
Senthil Kumaran wrote:
I am trying to compile vim from source with python
interpreter on Ubuntu. I have installed the dependencies for
vim, installed python2.7-devel and python2.7-dbg packages on
Ubuntu and do the configure step like this
./configure --enable-pythoninterp
Charles Campbell wrote:
So, how best to make this work? I was thinking
if has(win32) || has(win95) || has(win64) || has(win16)
if executable(cmd)
let g:netrw_localmovecmd= cmd move
endif
endif
No, as Ben said it would have to be cmd /c move and that's
just going to cause
John Beckett wrote:
letting the user know that netrw will
use 'move', 'mkdir', 'rmdir' as a default
I mean 'copy', not 'move'.
I wouldn't bother doing anything about it, but FYI line 3837:
if executable(start)
I just thought about this and checked. There is no executable
'start
Charles Campbell wrote:
I think it would be best to NOT test when under Windows
because there is no reasonable way to do so. If there were a
reasonable way for a script to store persistent data, you
could consider displaying a message the first time one of the
commands is invoked, letting the
smu johnson wrote:
In case anyone is curious, I'm trying to simulate the regular
searching slash key to be used to only search and
highlight, but _not_ jump to the next match.
Some good ideas are here:
http://vim.wikia.com/wiki/Highlight_all_search_pattern_matches
John
--
You received this
Taro MURAOKA wrote:
We holds translated Vim's documentation in Japanese at here.
http://vim-jp.org/vimdoc-ja/
Please add a link for it to http://www.vim.org/translations.php
Or who are best to ask it?
I added the information. You may need to reload the page in your
browser (flush cache) to
Val Markovic wrote:
Any help, advice or guidance would be greatly appreciated.
Someone needs to spend quality time:
1. Working out the problem is.
2. Fixing problem.
You could help point 1 by giving a brief indication of what the
problem is. Yes, the subject line tried to do that, but a few
Žroutík wrote:
I was trying to subscribe to the vim-dev list by email.
Therefore, I sent an email to vim-dev-subscr...@vim.org (see
below in the header of the original message) -- as requested
at http://www.vim.org/community.php
My email was delivered, but the subscription was unsuccessful
Bovy, Stephen wrote:
I have tried using this
source $VIMRUNTIME/mswin.vim
But I cannot get the copy and cut to put anything on the
clipboard
First step is to check output of :version to see if you have
+clipboard (feature supported) or -clipboard (not enabled
during build).
I do not know
Bovy, Stephen wrote:
When I use a Different X-Window Server this strange
esoteric problem completely disappears
I'm glad you have fixed the issue but for the future please use
the customs of this mailing list.
Your last message includes five copies of the standard email
footer which includes:
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 to email the maintainers
only ... wait, try
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 runtime files
they are in charge of?
Nothing is
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 make a suggestion.
It should be similar to the existing Vim repo, and Mercurial
should be available just as
What directories should the group manage?
A possibility is below, although it may be too ambitious. It
shows all first-level directories under runtime, with some to
be managed by a group, and the remainder run directly by Bram.
The files in 'runtime' would NOT be part of the group repo, but
all
Bram Moolenaar wrote:
What sign of modifier do you want against :8 ? :l ?
Or new function?
Currently :p turns any path into a full path, so that when
two names are expanded with :p they can be compared to find
out if they are equal.
Except for symlinks, that requires using resolve().
So
mattn wrote:
If :p (on Windows) always produced the expanded long name, then
:p:8 could be used if someone wanted the short full path.
No.
:echo fnamemodify('C:\Program Files', ':8:p')
C:\PROGRA~1
If there is a problem, please spell it out as the above is
correct.
I can't see a reason
1 - 100 din 188 matches
Mail list logo
