From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19392@debbugs.gnu.org
Subject: bug#19392: Emacs searches for dabbrevs in archive buffers
Date: Tue, 16 Dec 2014 17:19:06 +0100 [thread overview]
Message-ID: <CAG7BpappLoDTc84u3venwtzTdqFDVJSc=nFPecSQct+2oX93Dg@mail.gmail.com> (raw)
In-Reply-To: <83ppbjwqma.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
> What is the definition of "archive" for this purpose?
I would say any buffer that has certain major mode, e.g. 'archive-mode' or
'tar-mode'.
> Also, when you visit a .tar.gz file, isn't most of the buffer readable
> text (because Emacs automatically decompresses the archive)?
Yes, it appears readable, but dabbrev still comes with various "useful"
binary data. Perhaps another approach would be to not search for abbrevs in
hidden text, but I don't know how that is implemented internally and if it
would be easy enough.
Paul
[-- Attachment #2: Type: text/html, Size: 688 bytes --]
next prev parent reply other threads:[~2014-12-16 16:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 9:32 bug#19392: Emacs searches for dabbrevs in archive buffers Paul Pogonyshev
2014-12-16 15:39 ` Eli Zaretskii
2014-12-16 16:19 ` Paul Pogonyshev [this message]
2021-07-13 18:09 ` Lars Ingebrigtsen
2021-07-13 18:24 ` Paul Pogonyshev
2021-07-13 19:13 ` Lars Ingebrigtsen
2021-07-13 21:12 ` Paul Pogonyshev
2021-07-13 21:16 ` Paul Pogonyshev
2021-07-14 12:43 ` Eli Zaretskii
2021-07-14 16:19 ` Lars Ingebrigtsen
2021-07-14 17:37 ` Eli Zaretskii
2021-07-15 4:41 ` Lars Ingebrigtsen
2021-10-22 23:43 ` Stefan Kangas
2021-10-23 6:53 ` Eli Zaretskii
2021-10-23 7:47 ` Stefan Kangas
2021-10-24 12:25 ` Lars Ingebrigtsen
2021-10-24 13:07 ` Stefan Kangas
2021-10-24 13:19 ` Lars Ingebrigtsen
2021-10-24 14:27 ` Stefan Kangas
2021-10-24 19:59 ` Lars Ingebrigtsen
2021-07-14 16:15 ` Lars Ingebrigtsen
2022-05-07 11:20 ` Lars Ingebrigtsen
2022-05-07 12:19 ` Eli Zaretskii
2022-05-07 12:35 ` Lars Ingebrigtsen
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='CAG7BpappLoDTc84u3venwtzTdqFDVJSc=nFPecSQct+2oX93Dg@mail.gmail.com' \
--to=pogonyshev@gmail.com \
--cc=19392@debbugs.gnu.org \
--cc=eliz@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 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.