From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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 15:06:14 -0800 [thread overview]
Message-ID: <c57d39cc-cd60-6d11-c44b-1c44848f10c8@gmail.com> (raw)
In-Reply-To: <83k03q7khf.fsf@gnu.org>
On 11/19/2022 12:33 PM, Eli Zaretskii wrote:
>> 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.
Yeah, probably not. I'm not sure how important fixing this inconsistency
is, but if we *were* to fix it, I think the least-disruptive would be to
add a new option like "emacsclient --eval-one" that behaves like "emacs
--eval" and add an obsoletion warning to "emacsclient --eval". Then,
after a few versions, make "emacsclient --eval" work like "emacsclient
--eval-one".
This might be more effort than it's worth though...
> 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).
With the caveat that -f is already used for --server-file, I think this
would be fine. --funcall is a lot simpler to implement than --apply, at
least from emacsclient.
next prev parent reply other threads:[~2022-11-19 23:06 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 [this message]
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=c57d39cc-cd60-6d11-c44b-1c44848f10c8@gmail.com \
--to=jporterbugs@gmail.com \
--cc=59388@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--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.