zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: first adventures
Date: Sun, 26 Oct 2014 17:52:57 +0000	[thread overview]
Message-ID: <20141026175257.2611487b@pws-pc.ntlworld.com> (raw)
In-Reply-To: <544D2D6F.8030505@eastlink.ca>

On Sun, 26 Oct 2014 10:20:47 -0700
Ray Andrews <rayandrews@eastlink.ca> wrote:
> I'm trying to figure out where/how command lines are grabbed (I think 
> this is done by zle?).

That's how it works for interactive shells.  The lowest level of input
in the main shell is within input.c.  Because zle is a separate library
that may be loaded at run time the interaction actually goes through the
function zleentry() in init.c, which ensures that either zle is loaded
or if it can't be there's some fallback to get the input another way.
ZLE_CMD_READ is the command to zleentry() that causes a line to be read.

shingetline() is the fallback for non-interactive shells or if zle can't
be loaded.

> One other thing: 'make' produces so many dull msg. about moving
> into and out of directories and such.  Can these be turned off? I'd
> like to see just warnings and errors and 'important' msg.

make -s

pws


  parent reply	other threads:[~2014-10-26 17:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-26 17:20 Ray Andrews
2014-10-26 17:50 ` Bart Schaefer
2014-10-26 18:04   ` Bart Schaefer
2014-10-26 18:41     ` Ray Andrews
2014-10-26 19:57   ` Ray Andrews
2014-10-26 21:04     ` Bart Schaefer
2014-10-27  3:48       ` Ray Andrews
2014-10-27  6:08         ` Bart Schaefer
2014-10-26 17:52 ` Peter Stephenson [this message]
2014-10-28 17:48   ` Ray Andrews
2014-10-29  4:05     ` Bart Schaefer
2014-10-29 15:41       ` Ray Andrews
2014-10-29 20:46         ` Bart Schaefer
2014-10-29 23:31           ` Ray Andrews
2014-10-30  4:07             ` Bart Schaefer
2014-10-30 17:22               ` Ray Andrews
2014-10-31  1:59               ` Ray Andrews
2014-10-31  2:59                 ` 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=20141026175257.2611487b@pws-pc.ntlworld.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.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.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).