From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: 'run ahead' execution of script
Date: Tue, 24 Feb 2015 21:09:22 -0800 [thread overview]
Message-ID: <54ED5902.4020907@eastlink.ca> (raw)
In-Reply-To: <54ED40CB.5010005@pobox.com>
On 02/24/2015 07:26 PM, Andrew Janke wrote:
> From what i understand, it's not OS level; it's "Desktop Environment"
> level. The level that GNOME, KDE, et al live at, a few layers up the
> stack from the OS per se. On the Linux side, the semantics of that
> isn't entirely hashed out yet. For geany specifically, check out their
> "Sockets support" stuff, which governs how multiple geany processes
> interact. Looks like it's trying to be somewhat DE-agnostic. But is
> still primarily targeting invocation from a GUI environment, not a
> shell CLI.
>
> If you want a comparison, check out the `subl` command that's part of
> the Sublime Text distribution. Sublime Text is an editor that's native
> to the Mac OS X desktop environment, but provides a `subl` command
> adapter that has options for integration in to command line workflows.
> It's aware of how a persistent app (a graphical server, basically)
> would interact with individual invocations from shell sessions. In
> particular, it has a blocking "-w" option to "wait for files to be
> closed before returning" that does pretty much what you're looking for
> here. This might be a model for extending geany to work with
> shell-driven editing.
>
> Cheers,
> Andrew
Thanks Andrew, that's most interesting.
prev parent reply other threads:[~2015-02-25 5:09 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
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 [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=54ED5902.4020907@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).