From: Peter Vasil <mailing_lists@petervasil.net>
To: Bart Schaefer <schaefer@brasslantern.com>, zsh-workers@zsh.org
Subject: Re: edit-command-line problem with emacsclient
Date: Mon, 21 Sep 2015 21:09:24 +0200 [thread overview]
Message-ID: <560055E4.8080204@petervasil.net> (raw)
In-Reply-To: <150921120017.ZM426@torch.brasslantern.com>
Hi Bart,
Yes. both emacs and emacsclient accept [+LINE[:COLUMN]] FILENAME, so
that could be used in order to have only one case label for both.
Bests,
Peter
On 09/21/2015 09:00 PM, Bart Schaefer wrote:
> (Including Peter's entire message below because it didn't go to the list.)
>
> On Sep 21, 8:23pm, Peter Vasil wrote:
> }
> } I think for Emacs the current solution is the best and I would vote to
> } leaving it like it is right now.
>
> Yes, we'll probably have to add another case-label for emacsclient.
> Except:
>
> } emacsclient however accepts line and column alogn with the file name
> } like this: emacsclient [+LINE[:COLUMN]] FILENAME
>
> Ah! My manual page for emacsclient doesn't mention that. Emacs also
> accepts that. So we could replace "-eval (goto-char ...)" in both
> cases, and avoid having to split them?
>
>
>
>
> --- Forwarded mail from Peter Vasil <mailing_lists@petervasil.net>
>
> Subject: Re: edit-command-line problem with emacsclient
> To: Bart Schaefer <schaefer@brasslantern.com>
> From: Peter Vasil <mailing_lists@petervasil.net>
> Date: Mon, 21 Sep 2015 20:23:01 +0200
>
> Hi,
>
> I think for Emacs the current solution is the best and I would vote to
> leaving it like it is right now.
>
> To be honest, for emacsclient I would rather prefer the simple $EDITOR
> $1 call than the suggested solutions here in this thread. This worked
> out best.
>
> --create-frame or --tty depends really on the user's context, whether he
> uses the gui version or the terminal version. Do you really want to
> hardcode it in edit-command-line?
>
> emacsclient however accepts line and column alogn with the file name
> like this: emacsclient [+LINE[:COLUMN]] FILENAME
>
> Would it be possible to calculate LINE and COLUMN from byteoffset in zsh?
>
> Bests,
> Peter
>
next prev parent reply other threads:[~2015-09-21 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 11:46 Peter Vasil
2015-09-20 15:32 ` Bart Schaefer
[not found] ` <55FF3CE5.9070604@petervasil.net>
2015-09-21 4:06 ` Bart Schaefer
[not found] ` <56004B05.9000703@petervasil.net>
[not found] ` <150921120017.ZM426@torch.brasslantern.com>
2015-09-21 19:09 ` Peter Vasil [this message]
2015-09-21 21:16 ` Daniel Shahaf
2015-09-21 22:31 ` Bart Schaefer
2015-09-22 7:10 ` Peter Vasil
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=560055E4.8080204@petervasil.net \
--to=mailing_lists@petervasil.net \
--cc=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).