zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: first adventures
Date: Sun, 26 Oct 2014 14:04:39 -0700	[thread overview]
Message-ID: <141026140439.ZM14760@torch.brasslantern.com> (raw)
In-Reply-To: <544D5242.7000505@eastlink.ca>

On Oct 26, 12:57pm, Ray Andrews wrote:
}
} > No, that there isn't, though if you look around line 296 of input.c where
} > the VERBOSE option is handled, you'll get close.  The input line is read
} > into what's called "metafied" form by zleread() and has to be unmetafied
} But.  But ... we can't get the string before it's metafied in the first 
} place?

The following is a lot oversimplified, but:

It's read one character at a time and each character is then metafied
before being aggregated into the string buffer.

} How is it possible for it to be metafied before 'it' exists? If I can
} have a meta-fried egg, surely at some point there was a raw egg?

It's more like having a bag of popcorn; they don't all pop at the same
time, but ideally you don't open the bag until all of them have.

} I was looking in hist.c, because the one place where 
} things seem to be stored 'literally' is in .histfile.

History isn't stored until after bangchar references have been expanded, 
so although it's closer to literal it's still not the actual input line.

} The Tao of zsh is a deep thing.

Partly this is from separating ZLE into a module years after the shell
was first written.  It's designed so that somebody else could write and
plug in a different line editor module, but no one got that ambitious.

} But somehow I just can't get anything to print if interactive.

It works for me:

torch% echo hello
echo hello
hello
torch% 

Are you sure that you're actually executing the correct binary when you
are running interactively?  Maybe a startup file is "exec"-ing another
path?  What happens if you start zsh with the -v option?


  reply	other threads:[~2014-10-26 21:04 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 [this message]
2014-10-27  3:48       ` Ray Andrews
2014-10-27  6:08         ` Bart Schaefer
2014-10-26 17:52 ` Peter Stephenson
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=141026140439.ZM14760@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).