zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: 'run ahead' execution of script
Date: Tue, 24 Feb 2015 13:41:17 -0800	[thread overview]
Message-ID: <54ECEFFD.5010202@eastlink.ca> (raw)
In-Reply-To: <54ECD4B5.709@pobox.com>

On 02/24/2015 11:44 AM, Andrew Janke wrote:
> Yeah; the geany command's normal behavior isn't really suitable for a 
> CLI-driven editing session like this. You probably do want `geany -i`.

Sure, it's quite satisfactory, I'm just interested in seeing if there is 
a way for
zsh to handle it.  I think I understand the issue, but zsh can do some
impressive things, and maybe it can even test that the open file has been
saved, tho in a separate window/process.


>   e ) edit $1; echo "Sourcing $1"; source $1; return 0 ;;
                         ^

... maybe something can be put in there that says: 'proceed no further
until ...'.  I'm thinking that maybe the fact that zsh calls geany, tho
in another window, might give it some sort of 'handle' on it--seems
intuitive that it would, because otherwise if geany made some trouble--
crashed or something--zsh would be ... well, what would it be? Dunno,
but it's interesting.  Or maybe the protocol is that the two separate
shells have no crosstalk ... but that can't be true, because if you invoke
geany from any shell, it pops you over to whatever shell geany is
currently running in--so there is some communication.  Geany 'here'
knows that geany 'there' is already running.  But maybe zsh keeps its
nose out of that completely.  Geany is the only program I can think of
that does that sort of thing, which is a good reason why zsh might
not want anything to do with it.


  reply	other threads:[~2015-02-24 21:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 19:18 Ray Andrews
2015-02-24 19:44 ` Andrew Janke
2015-02-24 21:41   ` Ray Andrews [this message]
2015-02-25  2:21     ` Bart Schaefer
2015-02-25  2:46       ` Ray Andrews
2015-02-25  3:26         ` Andrew Janke
2015-02-25  5:09           ` Ray Andrews

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=54ECEFFD.5010202@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@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).