From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: gregory@heytings.org, xerusx@pm.me, 59388@debbugs.gnu.org
Subject: bug#59388: Open emacsclient file at last line
Date: Sun, 20 Nov 2022 21:00:20 +0200 [thread overview]
Message-ID: <83leo54fjv.fsf@gnu.org> (raw)
In-Reply-To: <e21ace7c-3181-98ad-6683-9d3049786ee3@gmail.com> (message from Jim Porter on Sun, 20 Nov 2022 10:49:10 -0800)
> Date: Sun, 20 Nov 2022 10:49:10 -0800
> Cc: gregory@heytings.org, xerusx@pm.me, 59388@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
>
> > Then I think I'm okay with adding --funcall to emacsclient, as a solution
> > for this feature request. With the proviso that the named function will be
> > called _after_ visiting the named FILE, right?
>
> Assuming it's possible, I think the most flexible, obvious, and
> consistent[1] way for it to work would be to obey the order of the
> arguments. So "emacsclient --funcall func file.txt" calls func and then
> visits file.txt, whereas "emacsclient file.txt --funcall func" visits
> file.txt and then calls func.
This won't work, because emacsclient thinks everything after the first FILE
cannot be an option. Which is why +LINE:COLUMN FILE works, although LINE
and COLUMN refer to FILE that comes after it.
We can invoke functions in the order of --funcall's, but they should run
after visiting the file. Nothing else makes sense, and was never possible
with emacsclient anyway.
So I stand by what I wrote: --funcall'ed functions should run after
visiting FILE. It's not a problem, as you can see from the implementation
of -position in the protocol.
next prev parent reply other threads:[~2022-11-20 19:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 11:57 bug#59388: Open emacsclient file at last line Janek F via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-19 15:48 ` Eli Zaretskii
2022-11-19 17:10 ` Gregory Heytings
2022-11-19 18:03 ` Eli Zaretskii
2022-11-19 18:07 ` Gregory Heytings
2022-11-19 18:17 ` Eli Zaretskii
2022-11-19 18:21 ` Gregory Heytings
2022-11-19 18:32 ` Eli Zaretskii
2022-11-19 19:05 ` Gregory Heytings
2022-11-19 19:37 ` Eli Zaretskii
2022-11-19 20:20 ` Gregory Heytings
2022-11-19 20:08 ` Jim Porter
2022-11-19 20:33 ` Eli Zaretskii
2022-11-19 23:06 ` Jim Porter
2022-11-20 7:22 ` Eli Zaretskii
2022-11-20 18:49 ` Jim Porter
2022-11-20 19:00 ` Eli Zaretskii [this message]
2022-11-20 19:37 ` Jim Porter
2022-11-21 8:55 ` Jean Louis
2022-11-21 13:36 ` Eli Zaretskii
2022-11-21 17:50 ` Jim Porter
2022-11-21 8:52 ` Jean Louis
2022-11-21 13:35 ` Eli Zaretskii
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=83leo54fjv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59388@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=jporterbugs@gmail.com \
--cc=xerusx@pm.me \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.