On 19 March 2014, Cade Forester ahx2...@gmail.com wrote:
Looks like you made a copy of f_sort() and modified it a bit. That's a
lot of duplicate code. Better move the common stuff into a function
that's used by both sort() and sortuniq().
Fixed
How about separating it from
Hi,
just have to share this here:
https://twitter.com/robertnyman/status/446547284915150848
Christ van Willegen
--
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
On Thu, Mar 20, 2014 at 4:04 AM, Christ van Willegen
cvwille...@gmail.comwrote:
just have to share this here:
https://twitter.com/robertnyman/status/446547284915150848
I agreed with that strongly. :D
Ben
--
b
--
--
You received this message from the vim_dev maillist.
Do not top-post!
Consider the following script:
LANG=ru_RU.UTF-8 vim -u NONE --cmd 'try|finally|catch|endtry'
. You will see message
E604: :catch без :finally: catch|endtry
which is translated from Russian as “:catch without :finally”. But with English
locale this message is the following:
E604:
On Thu, Mar 20, 2014 at 2:23 PM, ZyX zyx@gmail.com wrote:
Consider the following script:
LANG=ru_RU.UTF-8 vim -u NONE --cmd 'try|finally|catch|endtry'
. You will see message
E604: :catch без :finally: catch|endtry
which is translated from Russian as “:catch without :finally”.
Bohr Shaw wrote:
ehttps://raw.github.com/tpope/vim-sensible/master/plugin/sensible.vim
Hello!
Please try netrw v151n, available from my website:
http://www.drchip.org/astronaut/vim/index.html#NETRW .
For the optional url redirecting; you may disable netrw by putting
let
G.raud wrote:
if true
then
eval $varname=\\
# comment highlighted as a string
fi
Hello!
I haven't fixed this yet, but I wanted to let you know its on my todo list.
Chip Campbell
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
G.raud wrote:
To reproduce:
$ cat test.sh EOF
#!/bin/sh
myfunc () (
set -e
for arg; do
test -e $arg
done
if [ $# -gt 0 ]; then exit 1; fi
# no 'comment
)
$ vim -u NONE -c ':syntax on' test.sh
Hello:
I haven't
If you type `:bufdo $appendCR` vim will start iterating over buffers. Each
time buffer is entered $append asks for input. But
1. Buffer is not shown in the window, neither there are any messages about
which buffer is being processed.
2. It is hard to understand that cursor in the command-line
Consider the following script:
vim -u NONE -N -s (echo -E ':execute append\nabc\n.')
. It prompts for user input, but it is expected to act like
vim -u NONE -N -c 'execute append\nabc\n.'
which just appends abc.
--
--
You received this message from the vim_dev maillist.
Do not
The following script will echo 1 three times without any errors in place of
complaining about missing endif:
vim -u NONE 1 2 3 -c 'bufdo while 1 | echo 1'
. The following script will ask user three times for endif:
vim -u NONE 1 2 3 -s (echo ':bufdo if 1 | echo 1')
.
--
--
You
On 21/03/14 07:34, ZyX wrote:
The following script will echo 1 three times without any errors in place of
complaining about missing endif:
vim -u NONE 1 2 3 -c 'bufdo while 1 | echo 1'
I think you meant:
vim -u NONE 1 2 3 -c 'bufdo if 1 | echo 1'
doesn't complain about the missing
Documentation (quickfix.txt) defines the following incorrect abbreviations
Full | Listed | Correct
-- | -- | ---
caddexpr | cad| cadde
laddexpr | lad| ladde
caddbuffer | caddb | cad
laddbuffer | laddb | lad
--
--
You received this
On 21/03/14 07:34, ZyX wrote:
The following script will echo 1 three times without any errors in place of
complaining about missing endif:
vim -u NONE 1 2 3 -c 'bufdo while 1 | echo 1'
. The following script will ask user three times for endif:
vim -u NONE 1 2 3 -s(echo ':bufdo if
I think you meant:
vim -u NONE 1 2 3 -c 'bufdo if 1 | echo 1'
doesn't complain about the missing endif. As it happens, the while
example
doesn't complain either.
This or “in place of complaining about endwhile”, does not matter. Title says
about block commands, you will have the same
Isn't this to do with the fact that (...) causes the shell to create
a temporary file
It does not. It is =(...) that uses temporary files (assuming you use zsh),
(...) creates file descriptors before forking and attaches them to ...’s
stdout.
which is then sourced by ViM, and in ViM, all
Consider the following script:
execute 'if 0'
echo 'Not shown'
else
echo 'Shown'
endif
. If you source it you find that instead of 3 errors (“missing :endif”, “:else
without :if”, “:endif without :if”) and two messages (“Not shown” and “Shown”)
you will see one
Thanks! Can't wait the updated runtime.
On Thu, Mar 20, 2014 at 11:55 PM, Charles Campbell
charles.e.campb...@nasa.gov wrote:
Bohr Shaw wrote:
ehttps://raw.github.com/tpope/vim-sensible/master/plugin/sensible.vim
Hello!
Please try netrw v151n, available from my website:
On Thu, Mar 20, 2014 at 11:55:29AM -0400, Charles Campbell wrote:
Bohr Shaw wrote:
ehttps://raw.github.com/tpope/vim-sensible/master/plugin/sensible.vim
Hello!
Please try netrw v151n, available from my website:
http://www.drchip.org/astronaut/vim/index.html#NETRW .
For the optional url
19 matches
Mail list logo
