From: Jai Dayal <dayalsoap@gmail.com>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: send selection or current line to Terminal/iTerm
Date: Thu, 12 Jun 2014 14:31:49 -0600 [thread overview]
Message-ID: <CAMJ-YiRTN9WXvwYHnCrqgEff89_Q5s=QR25eXw_J5k0WtnouTQ@mail.gmail.com> (raw)
In-Reply-To: <87r42tvpkr.fsf@debian.uxu>
Correct, it's possible, but the applications that you're using have to be
programmed to expect information to come that way, right?
I'm surprised this has to be explained to you.
So, that's why I'm asking the OP how does Sublime Text do it with iterm?
On Thu, Jun 12, 2014 at 2:29 PM, Emanuel Berg <embe8573@student.uu.se>
wrote:
> Jai Dayal <dayalsoap@gmail.com> writes:
>
> > Well, how do you expect Emacs to interact with a
> > process executing outside of its context?
>
> What are you talking about? Of course that is
> possible!
>
> Ever heard of IPC, pipes, redirection, temporary files,
> shared clipboards, shared memory (or simply agreed-upon
> files on the same local disk), clients and servers,
> Emacs' executing shell commands, etc., etc.?
>
> --
> underground experts united:
> http://user.it.uu.se/~embe8573
>
next prev parent reply other threads:[~2014-06-12 20:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 20:58 send selection or current line to Terminal/iTerm klebsiella
2014-06-12 15:13 ` klebsiella
2014-06-12 15:49 ` Jai Dayal
2014-06-12 16:00 ` klebsiella
2014-06-12 16:02 ` Jai Dayal
[not found] ` <mailman.3500.1402588211.1147.help-gnu-emacs@gnu.org>
2014-06-12 20:29 ` Emanuel Berg
2014-06-12 20:31 ` Jai Dayal [this message]
[not found] ` <mailman.3510.1402605133.1147.help-gnu-emacs@gnu.org>
2014-06-12 20:36 ` Emanuel Berg
2014-06-12 20:43 ` Jai Dayal
2014-06-12 21:28 ` John Mastro
[not found] ` <mailman.3511.1402605838.1147.help-gnu-emacs@gnu.org>
2014-06-12 21:10 ` Emanuel Berg
2014-06-12 21:17 ` Jai Dayal
2014-06-12 21:43 ` klebsiella
2014-06-12 23:59 ` Jai Dayal
[not found] ` <CAOj2CQRaRpKuTTgseGjfhk504BLRJ=J+9C76nj+W6Px2iL9X1Q@mail.gmail.com>
2014-06-13 0:55 ` John Mastro
2014-06-13 13:39 ` klebsiella
2014-06-13 16:51 ` John Mastro
2014-06-14 2:30 ` John Mastro
2014-06-14 6:52 ` klebsiella
2014-06-14 14:22 ` Robert Thorpe
2014-06-14 15:09 ` klebsiella
2014-06-14 18:59 ` Robert Thorpe
[not found] ` <mailman.3652.1402758599.1147.help-gnu-emacs@gnu.org>
2014-06-17 14:11 ` Rusi
2014-06-17 15:58 ` klebsiella
2014-06-17 18:46 ` klebsiella
2014-06-17 19:55 ` John Mastro
2014-06-18 1:11 ` Robert Thorpe
2014-06-18 11:30 ` klebsiella
2014-06-14 16:52 ` John Mastro
2014-06-14 18:09 ` klebsiella
2014-06-14 18:36 ` John Mastro
2014-06-14 19:01 ` klebsiella
2014-06-14 19:24 ` John Mastro
2014-06-14 19:53 ` klebsiella
2014-06-14 15:31 ` Alan Schmitt
[not found] ` <mailman.3513.1402607827.1147.help-gnu-emacs@gnu.org>
2014-06-12 21:35 ` Emanuel Berg
2014-06-12 22:50 ` Robert Thorpe
[not found] ` <mailman.3499.1402586049.1147.help-gnu-emacs@gnu.org>
2014-06-12 15:47 ` Emanuel Berg
2014-06-12 21:26 ` Hans BKK
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMJ-YiRTN9WXvwYHnCrqgEff89_Q5s=QR25eXw_J5k0WtnouTQ@mail.gmail.com' \
--to=dayalsoap@gmail.com \
--cc=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).