From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: xerusx@pm.me, 59388@debbugs.gnu.org
Subject: bug#59388: Open emacsclient file at last line
Date: Sat, 19 Nov 2022 21:37:56 +0200 [thread overview]
Message-ID: <83sfie7n1n.fsf@gnu.org> (raw)
In-Reply-To: <518ded72c335e053d1c8@heytings.org> (message from Gregory Heytings on Sat, 19 Nov 2022 19:05:57 +0000)
> Date: Sat, 19 Nov 2022 19:05:57 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: xerusx@pm.me, 59388@debbugs.gnu.org
>
> > But if we do want to make this easier, I'd go with a new command-line
> > switch, say, "--eob". The Vim way is cryptic and error-prone, so I
> > don't think we should do the same. And I don't see at all why would
> > someone needs to say "N lines from EOF".
>
> One possible use case is "open a log file to look at the last N entries".
Going to EOB displays more than just the last line.
And the request was only to be able to go to EOB.
next prev parent reply other threads:[~2022-11-19 19:37 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 [this message]
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
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=83sfie7n1n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59388@debbugs.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.