On 8/31/06, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> On 8/30/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
>  > On 8/27/06, Martin Bähr <[EMAIL PROTECTED]> wrote:
> > > On Sun, Aug 27, 2006 at 05:36:21PM +0200, Axel Liljencrantz wrote:
> [rearranged]
>
> > Move left/right until we encounter a non-whitespace character.
> > Move left/right until we encounter a non-alphanumeric character.
> > If the character we stopped on is non-whitespace, move along one more 
> > character.
> >
> > I've played around with it and it seems to do what I want most of the
> > time. The actual rule may be a bit complicated, but the behaviour
> > seems to be what you would expect.
> [...]
>
> And symmetrically with deleting forward one word (Alt-D)?

Yes. They all use the same code.

>
> This rule sounds complicated.  I'm concerned that a user who tries to
> "discover" word deletion in Fish (without reading documentation) would
> not get the rule and would avoid deleting whole words.
>

The rule is complicated. My hope is that what the rule does is often
what you want, and that you won't realise that the underlying rule is
complicated because it's reslt is intuitive. Kind of like how
universal variables work.

>
> > Actually, I tried my version, and it didn't work. There where troubles
> > with tokens consisting completely of separateors. So the new rule for
> > move_word and kill_word is:
>
> Sorry, what were the troubles -- that you had to press Ctrl+W many
> times to delete many consecuitve separators?  With the new rule you
> would still have to press Ctrl+W many times, only one time less than
> with the simpler rule.  What is the rationale for making the first
> encountered separator more special than other separators?
>

The basic problem is that when a word ends with a a boundary
character, then ^W will only delete the whitespce after the word and
nothing of the word itself, which is hardly what the name implies, nor
is it very useful. You can get around this by having a special rule
like 'if you've never encountered an alphanumeric character, then you
may delete two types of non-alphanumeric characters, but this is at
least as complicated as the above rule, and still has various side
issues.

>
> [rearranged]
> > > the main problem is the need to be able to remove a whole argument
> > > conveniently. preferably without needing a seperate shortcut
>
> Does it have to be one keycombo press?
>
>
>
> > > > My interpretatin of your suggestion is that there should be two levels
> > > > of boundaries, one with whitespace and one with other boundary
> > > > characters, and that they be treated differently.
> [...]
>
> How about deleting till a boundary between any two of the three
> character sets whitespace, alphanumeric and

Still has the problem that hittin ^W on 'foo   ' will only delete
whitespace. No word is deleted by any reasonable definition.


-- 
Axel

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to