Re: ezmlm is broken; it can't unsibscribe me, it seems

2006-04-12 Thread Matthew Winn
he old address on it. (Unfortunately there's no requirement for the Received header to include that information so it may not work for you.) -- Matthew Winn ([EMAIL PROTECTED])

Re: ezmlm is broken; it can't unsibscribe me, it seems

2006-04-13 Thread Matthew Winn
eaders look correct to me, so it does seem as though the mailing list thinks your address is the one you're currently using. Oh well, it was just an idea and it turned out to be wrong :-( I think you're going to need to be removed from the list manually. -- Matthew Winn ([EMAIL PROTECTED])

Re: 7.0 administrivia

2006-05-09 Thread Matthew Winn
; } > > // Ah, this is now our little baby > : > : > } And if fork() returns -1? -- Matthew Winn ([EMAIL PROTECTED])

Re: 7.0 administrivia

2006-05-09 Thread Matthew Winn
On Tue, May 09, 2006 at 04:44:32PM +0200, Nikolai Weibull wrote: > On 5/9/06, Matthew Winn <[EMAIL PROTECTED]> wrote: > >On Tue, May 09, 2006 at 02:02:24PM +0200, Nikolai Weibull wrote: > >> Well, there's always the following algorithm to consider: > >> >

Re: All mails lost

2006-06-07 Thread Matthew Winn
nocent. I'm seeing your messages on the list. There have been situations in the past where the list has silently discarded messages because they don't match some arbitrary unpublished criterion, but that doesn't appear to be the case here. [cc'd to poster to be certain the mes

Re: scrolloff enhancement wish

2006-07-21 Thread Matthew Winn
e current line to a certain place on the screen, but at the time I was doing all this it was quicker to scroll the text each time than it would have been to write all the necessary mappings. > And we have too many options already... Too many options? Is that possible? -- Matthew Winn ([EMAIL PROTECTED])

Re: vim -S

2006-08-01 Thread Matthew Winn
im opens the script and executes it, but it ignores the first line because it sees it as a comment. -- Matthew Winn

Re: BOF Vim 8 - EncryptLine

2007-01-18 Thread Matthew Winn
t; ?> > > This has some advantages: [snip] > - Count of *'s is indicative of length of hidden area (user can add > whitespace padding to obscure when desired) That's a really bad idea. Anyone who shouldn't know what's there has absolutely no business knowing how long the obscured text is, and even those who know the password shouldn't need to care. If you're performing an assignment like $password = "some string" you don't really care what the content of the string happens to be, but only that it's assigned to a variable. -- Matthew Winn

Re: BOF Vim 8 - EncryptLine

2007-01-19 Thread Matthew Winn
this can already been done with g?$ (or g?a{ )...so if you only want > to protect your data from people looking over your shoulders, that's > already there. Gung'f ab tbbq. Erny areqf pna ernq ebg13 grkg jvgubhg hfvat fbsgjner. -- Matthew Winn

Re: Odp: BOF Vim 8 - Suggestions

2007-01-19 Thread Matthew Winn
erally takes users no more than a couple of seconds to realise that if the highlighting is distracting them all they have to do is enter a search that won't work, typically by dragging their fingers across the keyboard to create a string like "sdzdxfchgjbnk", and the highlighting has gone. -- Matthew Winn

Re: BOF Vim 8 - EncryptLine

2007-01-22 Thread Matthew Winn
to leave the file on the remote machine unattended. > Text editors don't do encryption and never should. How else would you ensure that you can have encrypted text _without_ the need to temporarily store a plaintext copy of the file? -- Matthew Winn

Re: improving encryption in vim

2007-03-19 Thread Matthew Winn
ther with anything less than the best encryption you can get? -- Matthew Winn

Re: improving encryption in vim

2007-03-20 Thread Matthew Winn
US abound, but also as Rijndael was the winning AES candidate the export of Rijndael implementations from the US is explicitly permitted. See the final paragraph of <http://csrc.nist.gov/CryptoToolkit/aes/aesfact.html> -- Matthew Winn

Re: feedkeys() allowed in sandbox

2007-04-29 Thread Matthew Winn
m does something similar, but in a way that's less complete. That's the right way to go about it. Setting an arbitrary limit and hoping it'll have the effect of improving security is far too optimistic for my tastes. -- Matthew Winn

Re: feedkeys() allowed in sandbox

2007-04-30 Thread Matthew Winn
On Sun, 29 Apr 2007 19:10:55 +1000, "John Beckett" <[EMAIL PROTECTED]> wrote: > Matthew Winn wrote: > > I don't like the idea of preventing modelines over 100 bytes. > > I imagine (haven't looked) that a modeline has no hard limit to > its length. So m

Re: feedkeys() allowed in sandbox

2007-05-03 Thread Matthew Winn
On Tue, 1 May 2007 19:42:02 +1000, "John Beckett" <[EMAIL PROTECTED]> wrote: > Matthew Winn wrote: > > If there was a security problem in Vim do you really think it > > couldn't be exploited in 100 characters? That's a pretty shaky > > foundation o

Re: Vim version 7.1a BETA has been released

2007-05-07 Thread Matthew Winn
ember that for all of cp, ln and mv, the existing file comes first. I think the confusion arises because people think of ln as "create a link", so they see "ln x y" as "create a link x...", which it isn't. It makes more sense if you think of it this way: mv x ymove file x to file y cp x ycopy file x to file y ln x ylink file x to file y -- Matthew Winn

Re: breakindent, take 2

2007-05-29 Thread Matthew Winn
ld be three styles? breakindent=nabsolute positioning or broken lines breakindent=+n broken lines have additional indentation breakindent=-n broken lines have reduced indentation -- Matthew Winn