zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu
Subject: Re: 'remove slash' bug
Date: Sun, 14 Jun 1998 14:16:38 -0700	[thread overview]
Message-ID: <980614141639.ZM315@candle.brasslantern.com> (raw)
In-Reply-To: <199806141357.NAA02238@tgape.ed.vnet>

On Jun 14,  1:56pm, TGAPE! wrote:
} Subject: Re: 'remove slash' bug
}
} Wayne Davison wrote:
} > 
} > Timothy J Luoma writes:
} >> However, there are times when I am in the middle of a path and do
} >> control-e to get to the end of the line, and the / I put in (and
} >> wanted) is removed.
} > 
} > I haven't managed to reproduce this problem, but I have been meaning
} > to look into a problem with the yank command being used right after
} > an auto-added slash.  I think the yank should leave the slash there
} 
} I can reproduce it.  Type
} 
} /usr<left to u><tab><control-e>

Hm.  What you describe isn't quite the same thing, but I think I've
finally got the original complaint figured out, based on what you say.

In order for the effect to happen, you must have all of autoremoveslash,
alwaystoend, and completeinword set.  Starting with this:

zsh% /usr/

Move the cursor to the 's'.  Press TAB.

3.0.5	-->	/usr/
3.1.4	-->	/usr//

In both cases, the cursor is at the end of the string.  Any following
key other than one bound to self-insert will delete the slash that is
immediately before the cursor.  In 3.1.4, this still leaves the original
slash behind, but it was wrong to have inserted a second slash in the
first place.  In 3.0.5, this (incorrectly?) deletes the only slash.

This also works starting with (say) /u/ or /us/, with the cursor on the
second slash or the 's'.

On Jun 14,  1:56pm, TGAPE! wrote:
} Subject: Re: 'remove slash' bug
}
} This is actually a more general problem, because it doesn't have to be a
} slash character which gets deleted.  It'll be whatever would be deleted
} with a backspace.

I can't come up with any case that deletes anything other than slashes or
spaces.  Here's how to get it to delete a space:

zsh% touch /tmp/foo
zsh% ls /tm/foo

Move the cursor to the 'm' and press TAB.  In both 3.0.5 and 3.1.4, this
produces "ls /tmp/foo " (note the trailing space).  In 3.1.4, typing any
further key other than self-insert deletes the trailing space.  3.0.5
leaves the space alone.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1998-06-14 21:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-07 22:41 Timothy J Luoma
1998-06-08  0:22 ` Bart Schaefer
1998-06-08  0:53   ` Timothy J Luoma
1998-06-08  3:56 ` Wayne Davison
1998-06-14 13:56   ` TGAPE!
1998-06-14 21:16     ` Bart Schaefer [this message]
1998-06-15  6:49       ` Mircea Damian
1998-06-15 16:34         ` Timothy J Luoma
1998-06-15 16:35       ` Peter Stephenson
1998-06-16  5:21         ` Bart Schaefer
1998-06-16  9:41           ` Peter Stephenson
1998-06-21 18:01 Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=980614141639.ZM315@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).