* bug#18335: 24.4.50; Typo: title of `enriched.txt' is `enriched.el'
@ 2014-08-27 4:32 Drew Adams
2014-08-27 4:51 ` Glenn Morris
0 siblings, 1 reply; 3+ messages in thread
From: Drew Adams @ 2014-08-27 4:32 UTC (permalink / raw)
To: 18335
Presumably, someone renamed the file and forgot to update the title at
the top of the text. This oublie predates even Emacs 20, it seems, for
there the file is named `enriched.doc' (it is the same file, with the
same name, for Emacs 24.3 and prior) but the title remains
`enriched.el'.
But I wonder about this: The file was presumably originally
`enriched.el', and so presumably in Emacs Lisp mode. The Emacs manual,
node `Enriched Text' currently says this:
Enriched mode is typically used with Text mode (*note Text Mode::).
It is _not_ compatible with Font Lock mode, which is used by many major
modes, including most programming language modes, for syntax
highlighting (*note Font Lock::). Unlike Enriched mode, Font Lock mode
assigns text properties automatically, based on the current buffer
contents; those properties are not saved to disk.
I would like to know more about just what this incompatibility amounts
to. This text is new with Emacs 24.4, and there is no more explanation
than that. Why was this added? Why not let users know what it means?
If you mean only that font-lock highlighting interferes with
enriched-mode highlighting, that is one thing - and in this,
enriched-mode is no different from other highlighting using
text-property `face'. If you something stronger wrt incompatibility,
then please document what it is.
In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
of 2014-06-28 on ODIEONE
Bzr revision: 117431 rgm@gnu.org-20140628015517-eku6hj8mpgcvfnso
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/snapshot/trunk
--enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
-Ic:/Devel/emacs/include''
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#18335: 24.4.50; Typo: title of `enriched.txt' is `enriched.el'
2014-08-27 4:32 bug#18335: 24.4.50; Typo: title of `enriched.txt' is `enriched.el' Drew Adams
@ 2014-08-27 4:51 ` Glenn Morris
2014-08-27 5:06 ` Drew Adams
0 siblings, 1 reply; 3+ messages in thread
From: Glenn Morris @ 2014-08-27 4:51 UTC (permalink / raw)
To: 18335-done
Drew Adams wrote:
> the title remains `enriched.el'.
It's describing the features of enriched.el.
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#18335: 24.4.50; Typo: title of `enriched.txt' is `enriched.el'
2014-08-27 4:51 ` Glenn Morris
@ 2014-08-27 5:06 ` Drew Adams
0 siblings, 0 replies; 3+ messages in thread
From: Drew Adams @ 2014-08-27 5:06 UTC (permalink / raw)
To: Glenn Morris, 18335-done
> > the title remains `enriched.el'.
>
> It's describing the features of enriched.el.
Well of course it does that - anything that describes Enriched mode
does that. But it certainly is not describing `enriched.el'.
It tells you nothing about the code.
And Emacs does not introduce this file to its users as something
that describes `enriched.el'. Not at all. This is how Emacs
introduces the file to users - in (emacs) `Enriched Text':
The file `enriched.txt' in Emacs's `data-directory' serves as an
example of the features of Enriched mode.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The file serves as our primary example, for ordinary users (not
necessarily Lispers), of Enriched mode. It is end-user doc about
Enriched mode. It is not an explanation or description of
`enriched.el'.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-08-27 5:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-08-27 4:32 bug#18335: 24.4.50; Typo: title of `enriched.txt' is `enriched.el' Drew Adams
2014-08-27 4:51 ` Glenn Morris
2014-08-27 5:06 ` Drew Adams
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).