zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: <zsh-workers@sunsite.auc.dk>
Subject: Re: New compinstall and bindkey
Date: Tue, 29 Jun 1999 16:03:43 +0000	[thread overview]
Message-ID: <990629160343.ZM21855@candle.brasslantern.com> (raw)
In-Reply-To: <000c01bec222$308cc100$21c9ca95@mow.siemens.ru>

On Jun 29,  3:26pm, Andrej Borsenkow wrote:
} Subject: RE: New compinstall and bindkey
}
} > Firstly, the new compinstall doesn't seem to work very will when the
} > functions have been installed in subdirectories: It refuses to accepy
} > /usr/local/share/zsh/functions as the directory containing the
} > functions.

I was going to complain about this myself.  Not only that, but I somehow
managed to get it to set FPATH to a string consisting of a space-separated
list of the dirs in which the functions were installed.  (That made it as
easy as "vared fpath<RET><RET>" to get the path set correctly, but it sure
was confusing.)

} > How do I bind a key to insert a new-line without doing an accept-line.
} > In the zed function it is done with bindkey "^M" self-insert-unmeta but
} > this binds it to return. I was hoping to bind it to Alt-Return.
} >
} 
} Hmmm ... in command line editing multiline input I can insert new line by
} pressing ^V^J.

I can insert one with ESC-return, and though "bindkey -m" doesn't make that
equivalent to alt-return, "bindkey '\M-\C-M' self-insert-unmeta" does so.

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


      parent reply	other threads:[~1999-06-29 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-28 14:44 Oliver Kiddle
1999-06-29 11:26 ` Andrej Borsenkow
1999-06-29 13:48   ` new menu selection and " Oliver Kiddle
1999-06-29 16:03   ` Bart Schaefer [this message]

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=990629160343.ZM21855@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.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).