From: Wayne Davison <wayned@users.sourceforge.net>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: <zsh-workers@sunsite.dk>
Subject: Re: vi editting troubles
Date: Wed, 23 May 2001 11:18:05 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33L2.0105231114560.12475-100000@phong.blorf.net> (raw)
In-Reply-To: <200105230708.JAA21752@beta.informatik.hu-berlin.de>
On Wed, 23 May 2001, Sven Wischnowsky wrote:
> Repeating everything in every function is just too ugly.
> Putting it into the C-code is the opposite of what I wanted to achieve --
> and I want to try to keep the basic C-code independent of the way the
> completion system shell code is written.
An off-the-cuff suggestion: Would it be possible to have the C code
call a "set completion defaults" shell function, store these default
values, and then automatically restore them before any call out to the
completion system? Would that accomplish your desired goal of keeping
the C-code independent?
..wayne..
next prev parent reply other threads:[~2001-05-23 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 3:04 Paul Ackersviller
2001-05-23 4:41 ` 64-bit sparc instructions Bart Schaefer
2001-05-23 9:38 ` Andrej Borsenkow
2001-05-23 16:42 ` Clint Adams
2001-05-23 12:29 ` Clint Adams
2001-05-23 6:28 ` vi editting troubles Bart Schaefer
2001-05-23 7:08 ` Sven Wischnowsky
2001-05-23 9:42 ` Peter Stephenson
2001-05-23 18:18 ` Wayne Davison [this message]
2001-05-23 19:31 ` Bart Schaefer
2001-05-29 6:59 ` Sven Wischnowsky
2001-05-29 11:57 ` PATCH: " Sven Wischnowsky
2001-05-29 14:58 ` Bart Schaefer
2001-05-30 7:19 ` Sven Wischnowsky
[not found] <20010521121334.A24931@flora01.SLAC.Stanford.EDU>
2001-05-21 19:43 ` Peter Stephenson
[not found] ` <010521132805.ZM11030@candle.brasslantern.com>
2001-05-22 1:53 ` nce
2001-05-22 2:31 ` 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=Pine.LNX.4.33L2.0105231114560.12475-100000@phong.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.dk \
/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).