unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: era+emacs@iki.fi, 20891@debbugs.gnu.org
Subject: bug#20891: emacs: Back off if .doc is not an Office document
Date: Wed, 06 Nov 2019 02:53:21 +0100	[thread overview]
Message-ID: <87pni54vou.fsf@marxist.se> (raw)
In-Reply-To: <875zngd2v4.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Thu, 01 Aug 2019 22:53:19 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> era+emacs@iki.fi writes:
>
>> It is not uncommon for *.doc files to contain plain ASCII text. In this
>> case, the default behavior of Emacs is less than ideal, as described in
>> more detail in the problem report below. Perhaps the .doc file name
>> mapping should contain some additional heuristics, and fall back to
>> plain text if the file is not an Office document.
>
> (I'm going through old bug reports that have unfortunately not gotten
> any responses.)
>
> I think this makes sense.  A fix in Emacs would mean moving the .doc
> recognition from `auto-mode-alist' to...  `magic-fallback-mode-alist', I
> guess.
>
> According to the interwebs, the magic sequence for Word .doc files is:
>
> D0 CF 11 E0 A1 B1 1A E1
>
> Does anybody have an opinion here?

I wasn't aware of the practice to name plain text files *.doc; I can't
remember having encountered any file like that.  Perhaps this practice
is rare.

Would implementing this risk make opening *.doc files slower for most
users?  Perhaps that could make the trade-off not worth it.  Other
than that, I see no problem with the proposal.

Best regards,
Stefan Kangas





  reply	other threads:[~2019-11-06  1:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 11:19 bug#20891: emacs: Back off if .doc is not an Office document era+emacs
2019-08-01 20:53 ` Lars Ingebrigtsen
2019-11-06  1:53   ` Stefan Kangas [this message]
2019-11-06 13:08     ` era
2019-11-06 23:19       ` Stefan Kangas
2019-11-07  4:45         ` Richard Stallman
2019-11-07  8:29           ` era
2019-11-08 20:59     ` Lars Ingebrigtsen
2019-11-09  6:25       ` Eli Zaretskii
2019-11-09 20:14         ` Lars Ingebrigtsen
2019-11-14  8:54           ` Eli Zaretskii
2019-11-14  9:55             ` Lars Ingebrigtsen
2019-11-14 14:12               ` Eli Zaretskii
2019-11-14 15:06                 ` Robert Pluim
2019-11-14 16:19                   ` Eli Zaretskii
2019-11-14 16:33                     ` Andreas Schwab
2019-11-14 16:42                       ` Eli Zaretskii
2019-11-15  7:51                         ` Lars Ingebrigtsen
2019-11-15  8:48                           ` Eli Zaretskii
2019-11-15  8:56                             ` Lars Ingebrigtsen
2019-11-15  9:51                               ` Eli Zaretskii
2019-11-15 13:20                                 ` Robert Pluim
2019-11-15  9:14                         ` Robert Pluim
2019-11-15  7:50                 ` 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

  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=87pni54vou.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=20891@debbugs.gnu.org \
    --cc=era+emacs@iki.fi \
    --cc=larsi@gnus.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).