From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jim Porter <jporterbugs@gmail.com>,
gregory@heytings.org, xerusx@pm.me, 59388@debbugs.gnu.org
Subject: bug#59388: Open emacsclient file at last line
Date: Mon, 21 Nov 2022 11:55:34 +0300 [thread overview]
Message-ID: <Y3s9BlDwLcf8gv22@protected.localdomain> (raw)
In-Reply-To: <83leo54fjv.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2022-11-20 22:01]:
> 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.
I use `-e' to open new frame seeking for specific buffer, or invoking
specific functions.
> 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.
--funcall is similar as `-e' only limited to single function. So I
suggest that when you implement that, that --funcall may be used
also without any file, such as emacsclient -c --funcall my-function
as that way I can invoke necessary programs.
Though it is not logical to tie a "funcall" to file, file may not be
there, or it could be new file, or new frame created, or --funcall can
do useful things in the existing server.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-11-21 8:55 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
2022-11-20 19:37 ` Jim Porter
2022-11-21 8:55 ` Jean Louis [this message]
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
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=Y3s9BlDwLcf8gv22@protected.localdomain \
--to=bugs@gnu.support \
--cc=59388@debbugs.gnu.org \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).