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: Sat, 19 Nov 2022 22:33:16 +0200 [thread overview]
Message-ID: <83k03q7khf.fsf@gnu.org> (raw)
In-Reply-To: <4dff4be5-8c53-8d8b-e912-1cf2bb3dff98@gmail.com> (message from Jim Porter on Sat, 19 Nov 2022 12:08:06 -0800)
> Date: Sat, 19 Nov 2022 12:08:06 -0800
> Cc: xerusx@pm.me, 59388@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
>
> 1. Why does --eval do that? You can mix filenames and --eval with the
> regular emacs program:
>
> emacs -Q foo.txt --eval '(message "hi")'
>
> Why doesn't emacsclient work similarly? (On the other hand, changing
> this might break compatibility, so we should be careful here.)
I don't think we can change the semantics of --eval.
> 2. Assuming we don't change --eval as above, maybe the proposed --apply
> option discussed in bug#57752 could work:
>
> emacsclient --apply end-of-buffer -- foo.c
>
> I believe this would even work if you defined a shell alias like so:
>
> alias edit=end="emacsclient --apply end-of-buffer --"
> edit-end foo.txt
>
> That said, adding --apply to emacsclient (and emacs, too!) seemed
> like a fair bit of work when I looked at it...
Maybe we don't need to go as far as that discussion led us? Just adding a
switch --funcall, to mimic what Emacs has, could be enough? Then we'd be
able to say
emacsclient -f eob FILE
(assuming we also add a function 'eob' to Emacs).
next prev parent reply other threads:[~2022-11-19 20:33 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 [this message]
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
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=83k03q7khf.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.