From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: bzg@altern.org, 15947@debbugs.gnu.org
Subject: bug#15947: DocView interferes with etc/enriched.doc
Date: Fri, 22 Nov 2013 20:02:18 +0200 [thread overview]
Message-ID: <83li0gco2d.fsf@gnu.org> (raw)
In-Reply-To: <rftxf4qsfr.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Date: Fri, 22 Nov 2013 12:04:08 -0500
> Cc: 15947@debbugs.gnu.org
>
> I think just using .txt for the example file would be better than making
> up a new extension.
Exactly my thoughts.
next prev parent reply other threads:[~2013-11-22 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 18:22 bug#15947: DocView interferes with etc/enriched.doc Glenn Morris
2013-11-21 18:35 ` Glenn Morris
2013-11-22 9:31 ` Bastien
2013-11-22 17:04 ` Glenn Morris
2013-11-22 18:02 ` Eli Zaretskii [this message]
2013-11-22 18:27 ` Bastien
[not found] ` <olvbzjhn5t.fsf@fencepost.gnu.org>
2022-01-26 17:14 ` Lars Ingebrigtsen
2022-02-23 20:14 ` 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=83li0gco2d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15947@debbugs.gnu.org \
--cc=bzg@altern.org \
--cc=rgm@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).