unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: Status of shell-pcomplete integration?
Date: 04 Dec 2002 10:31:05 +0900	[thread overview]
Message-ID: <buoadjmvacm.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <87of83qbjp.fsf@alice.dynodns.net>

John Wiegley <johnw@gnu.org> writes:
> > The behavior can later on be changed, but at first we should just
> > concentrate on getting pcomplete to behave "like the current code".
> 
> As long as it gets changed before 21.3 goes out?  I tell you, no one
> will know its there, and nobody will get the benefit of using it.

Maybe so, but you can argue that later.  It's a minor issue.

[BTW, I tried pcomplete-cycle-completions for a while, and hated it.
 It makes much less sense in emacs, which can show a list of
 completions and then restore the screen, than it does in a shell,
 which can't.]

-Miles
-- 
I'm beginning to think that life is just one long Yoko Ono album; no rhyme
or reason, just a lot of incoherent shrieks and then it's over.  --Ian Wolff

  reply	other threads:[~2002-12-04  1:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-01 14:22 Status of shell-pcomplete integration? Romain FRANCOISE
2002-12-01 15:47 ` Kai Großjohann
2002-12-01 22:48   ` John Wiegley
2002-12-02 16:40     ` Kai Großjohann
2002-12-03  7:42     ` Kai Großjohann
2002-12-03 10:37       ` Romain FRANCOISE
2002-12-03 15:53         ` Kai Großjohann
2002-12-03 16:14           ` John Wiegley
2002-12-03 16:28             ` Romain FRANCOISE
2002-12-03 16:28             ` Stefan Monnier
2002-12-03 17:04               ` John Wiegley
2002-12-04  1:31                 ` Miles Bader [this message]
2002-12-03 17:52               ` Kai Großjohann
2002-12-03 16:23           ` Romain FRANCOISE
2002-12-03 17:05             ` John Wiegley
2002-12-05 10:39               ` Kai Großjohann
2002-12-02 11:20   ` Mario Lang
2002-12-03 14:59 ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=buoadjmvacm.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).