h the possibility that someone might set a value of
"10,20,15", so not having to catch that and issue an error message was
an additional factor in the design.)
--
Matthew Winn
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below
On 13/03/18 06:47, Nikolay Aleksandrovich Pavlov wrote:
2018-03-13 9:09 GMT+03:00 Matthew Winn :
How many people will use it is irrelevant. The point I'm trying to make here
is that all the opposition has been based around objections that have never
been used to object to other features.
On 12/03/18 22:06, Nikolay Aleksandrovich Pavlov wrote:
2018-03-12 0:36 GMT+03:00 Matthew Winn :
But editing tabular information is something that a great many people do.
It's not just a matter of working with tab-separated data files. How often
do you want to assemble columns of informati
" or "I wish Vim was programmable in my favourite
language". Those are developer requirements. Variable tabstops are an
end-user feature: a basic function that's of use to everyone rather than
an advanced addition that only experts will care about. Shouldn't
end-user
s what I did. You even chipped in
with suggestions for improvements while I was working on it. Don't you
think that if you ask people to help implement features that you don't
have the time to work on yourself you have an obligation to accept
working patches from people who do exactly as y
ne is THE match.
--
Matthew Winn
--
--
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 http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Goog
though it has been done. Its test suite at the time
was test65; the number of tests has more than doubled since then.
--
Matthew Winn
--
--
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 informa
nd it's an easy mistake
to make for anyone who routinely writes in multiple languages. It's more
helpful to have the mistake flagged up by unexpected syntax highlighting
than to wait for the compiler - or worse, the program itself - to point
out the problem.
--
Matthew Winn
--
--
You r
capture plaintext
being sent to the external program. (I've seen exactly this technique
used to capture credit card numbers.)
--
Matthew Winn
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mo
. So, not only do we get data privacy with
Blowfish, but we get authentication with HMAC-SHA256.
Shouldn't that sort of task be delegated to an external application? Vim
is a text editor, not an evidential data integrity suite.
--
Matthew Winn
--
--
You received this message from the &qu
that users wanted back in 2007 or so - that's
why I chose it as my contribution to the community - and it's far safer
than many of the features added since then.
--
Matthew Winn
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your r
a precedent. For example, if you set 'textwidth' then the value of
'wrapmargin' is ignored, and if you set 'binary' then a whole host of
options are ignored.
--
Matthew Winn
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
ses. So if
> anybody is interested in that patch and likes to try it out, here is it.
Thanks. I'd like to use it again myself but I won't have time to look at it
for a couple of weeks.
--
Matthew Winn
--
--
You received this message from the "vim_dev" maillist.
Do not t
On Tue, 21 May 2013 09:51:37 -0700 (PDT), Kirill Serkh
wrote:
> In 2007 Matthew Winn published a patch against vim 7.1.135 for non-uniform
> tabstops (i.e. setting tabstops at user-defined columns) [1]. It was voted on
> in 2008 [2] but never made its way into vim (?).
[snip]
> I
at it wasn't a good idea to have multiple
values in the "tabstop" option in case someone tried to treat its
value as a number, so I eventually settled on "vartabstop" as the name
of the option.
--
Matthew Winn
--
You received this message from the "vim_dev" mai
depends on the floating-point hardware, if there is any.
I remember hearing of systems that didn't have Inf or NaN but I don't
remember using one myself.
--
Matthew Winn
--
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 http://www.vim.org/maillist.php
On Mon, 07 Jun 2010 16:07:05 +0200, Ingo Karkat
wrote:
> There is a "variable tabstops" patch by Matthew Winn; it's listed on the Vim
> patches page (http://groups.google.com/group/vim_dev/web/vim-patches):
>
> 10. Variable tabstops
> Author: Matthew Winn
&g
d ends of the pipes in /both/ those processes. You should end
up with only pipe_in[1] open in the parent and only pipe_out[0] open
in the second child.
(Unless I got confused.)
--
Matthew Winn
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
recent version is available in vim-extended.
I'd like to thank Lech Lorens for updating the patch. Unfortunately my
development environment died last year and it's not easy to get parts
for a fourteen year old system at prices I'm willing to pay, so I'm
currently Unixless and com
rvened.
I'll see if I can find the time to bring the patch up to date.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
did try that but it's trickier than it sounds. 'vts' allocates
memory for a parsed copy of the tabstops, and keeping track of that
memory when setting ts was excessively complicated so I opted for a
simpler "ignore ts if vts is set" strategy instead. I'll take another
l
d forget that you've done it then setting ts appears broken because
it doesn't do anything. (I spent quite a long time trying to work out
why I couldn't change the tabstop setting, only to discover that I was
setting vts in my .vimrc for testing and that was overriding ts.)
I shou
hostnames which violate this rule (411.org, 1776.com).
The presence of underscores in a label is allowed in [RFC 1033],
except [RFC 1033] is informational only and was not defining
a standard.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message
ave the same inode. I'm not sure how you would do so for other
> OSes.
The same device number and inode number, to be precise.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
On Sun, 20 Jul 2008 20:42:21 +1000, Ben Schmidt
<[EMAIL PROTECTED]> wrote:
> Matthew Winn wrote:
> > On Sun, 20 Jul 2008 00:44:48 +1000, Ben Schmidt
> > <[EMAIL PROTECTED]> wrote:
> >
> >> As has been pointed out, making a directory in /tmp is mor
d removes Vim's temp directories, and since a long-running Vim
> process created the directory, it assumes it's there and doesn't
> recreate it but just gives errors.
Shouldn't it only clear out things that haven't been used for a while?
The whole point
ovide a general way of defining paragraphs rather than dealing with
one specific special case.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
he moment, but
what happens when a part of the file not including the first line of
the buffer is filtered through an external command? Should the BOM be
added to the start of the filtered text and removed afterwards?
I suppose it all depends on whether the BOM is considered to be part
of the buffer
ity
in the regular expression language was abandoned years ago in favour
of functionality.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
e) headers use whitespace at the start of a line to
indicate that the line is a continuation of the line above.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
ver an entire file. An extended idea
is to find some way of specifying different tab widths at different
parts of the same file, but that means a heap of empty cans and worms
all over the place.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from th
ame thing. I'll look into it presently.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
f
> vim.
Thanks. I tried out your script and it works very well. When I get the
time I'll update the patch to the latest patch of Vim, as my patch is
against 7.1.145.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the &quo
rom Vim and then exit the shell, Vim bombs out with a
message about being unable to read its input. I tried to work out what
was happening but had trouble understanding how a child process could
influence its parent in that way. In the end I gave up and "fixed" the
problem by using an old
atting style was
"add a line break when I get near the right side of the screen". His
objective was to get as much code on one screen as possible. As far as
I know he was the only person who was ever able to understand his own
code, and ever
usly useful.
>
> Stay tuned for any comments I have after I try it!
Thanks.
There's a small problem with the patch as it stands, though it doesn't
affect any functionality. I forgot to wrap the functions at the end of
option.c in an #ifdef, so if someone compiles with the variable wid
take away the possibility of adding a "; register in
the future.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
On Sat, 6 Oct 2007 21:41:22 +0200, "Yakov Lerner" <[EMAIL PROTECTED]>
wrote:
> On 10/6/07, Matthew Winn <[EMAIL PROTECTED]> wrote:
> >
> > :set ts=5,7 ts+=3 ts?
> > tabstop=5,73
> >
> > Not a very useful ability.
>
> Wron
On Sat, 6 Oct 2007 10:22:53 +0200, "Yakov Lerner" <[EMAIL PROTECTED]>
wrote:
> On 10/5/07, Matthew Winn <[EMAIL PROTECTED]> wrote:
> >
> > I've been working on an implementation of the non-uniform tabstops
> > that were discussed about a month
functions at the
bottom of option.c. The only detail of the implementation that has
leaked out to the rest of Vim is the int* type of the variables.
This patch is against 7.1.135.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the
ected all the
> tabstops
> and everything else to be pushed backward by the 'showbreak' string as well.
That's what I'd have expected.
> If I have some time, I'll have a look at this, but don't expect I will for at
> least a week!
I'm going to be looking at it too. It's bugging me, not knowing what's
going on.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
re the cursor goes after each movement. On some of the
wrapped lines I see it settle three characters to the left of where it
should be when it moves to the first word on each wrapped screen line.
I've tried to fix it, but no matter what I change the cursor always
lands in the wrong place
already know. A few years ago I was in
Antwerp and several native speakers of Flemish/Dutch said they found
English a laughably easy language to learn, and they certainly spoke
excellent English to me. On the other hand I imagine someone whose
native language was Latin would
first line to the start of the second, making the ends
of the lines appear more regular.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
alalways. Perhaps
> this patch should support a 'pseudoeuqalalways' option?
:set equalmostly?
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
r
been happy with the way equalalways worked because with it on it
wrecked my small window every time I split the main window, and with
it off three successive splits mean I'm left working in an eighth of
the available space instead of a quarter: typically four lines in the
active window inste
t their staff can't even set up mailing list software.
I could do better than that.
--
Matthew Winn
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
47 matches
Mail list logo
