From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Alfred M. Szmidt" <ams@gnu.org>, emacs-devel@gnu.org
Subject: Re: replacing hexl-mode with nhexl-mode?
Date: Wed, 23 Mar 2022 12:47:23 -0400 [thread overview]
Message-ID: <jwv4k3oipxa.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83lex0et0w.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Mar 2022 14:46:07 +0200")
> Feel free to fix that, but at least on my system not all of the issues
> I see are solved when I visit the file literally: the jagged display
> at the right is still there. I guess it's somehow caused by the glyph
> used to display the LF character (and I expect the same to happen for
> TABs), but it is still ugly and should be fixed, IMO.
Indeed, `nhexl-mode` was not designed as a plug-in replacement for
`hexl-mode`. If there's a real desire to replace `hexl-mode` with
`nhexl-mode` then Someone™ will need to go and fill those holes.
> Another missing feature is the ability to mark and copy the hex
> display part. hexl supports it, but nhexl doesn't, it seems: it can
> only copy from the right column, where the actual file's contents are
> listed, but not from the hex display part.
I vaguely remember working on getting some of that working, but I don't
think it's possible to make it work 100% like in hexl-mode (IIRC you
needed to get into `nhexl-nibble-mode` in order to copy/paste the hex
text and then there's the question of whether that should copy only the
hex text, or the combined hex+nonhex text, etc...).
Stefan
next prev parent reply other threads:[~2022-03-23 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 16:49 replacing hexl-mode with nhexl-mode? Alfred M. Szmidt
2022-03-22 17:59 ` Eli Zaretskii
2022-03-22 19:37 ` Alfred M. Szmidt
2022-03-22 20:03 ` Eli Zaretskii
2022-03-22 20:41 ` Eli Zaretskii
2022-03-23 7:07 ` Alfred M. Szmidt
2022-03-23 12:46 ` Eli Zaretskii
2022-03-23 16:47 ` Stefan Monnier [this message]
2022-03-25 6:59 ` Alfred M. Szmidt
2022-03-25 7:08 ` 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=jwv4k3oipxa.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=ams@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).