Skip to content

many .xml files for the User's Manual force xml-mode in emacs

Many (all?) of the XML files for the User's Manual contain the following or similar:

<!-- Emacs stuff:
     ;;; Local Variables: ***
     ;;; mode: xml ***
     ;;; sgml-parent-document: ("users_guide.xml" "book" "chapter" "sect1") ***
     ;;; End: ***
 -->

The "mode:" line, in particular (assuming the user hasn't disabled the feature) overrides the user's choice of mode for XML editing (when the filename ends in .xml or another common XML suffix, anyway). Since I use nxml-mode, not xml-mode, this bothers me.

A quick grep turns up:

cd /home/naesten/hacking/haskell/ghc-hashedrepo/docs/users_guide/
grep -n -e 'mode: xml' --recursive . /dev/null
./runghc.xml:39:     ;;; mode: xml ***
./packages.xml:1271:     ;;; mode: xml ***
./5-00-notes.xml:204:     ;;; mode: xml ***
./using.xml:1848:     ;;; mode: xml ***
./utils.xml:561:     ;;; mode: xml ***
./glasgow_exts.xml:7546:     ;;; mode: xml ***
./license.xml:63:     ;;; mode: xml ***
./ug-book.xml.in:28:     ;;; mode: xml ***
./bugs.xml:404:     ;;; mode: xml ***
./6.0-notes.xml:316:     ;;; mode: xml ***
./debugging.xml:624:     ;;; mode: xml ***
./5-04-notes.xml:285:     ;;; mode: xml ***
./win32-dlls.xml:633:     ;;; mode: xml ***
./5-02-notes.xml:54:     ;;; mode: xml ***
./ghci.xml:2827:     ;;; mode: xml ***
./flags.xml:2341:     ;;; mode: xml ***
./lang.xml:12:     ;;; mode: xml ***
./separate_compilation.xml:1261:     ;;; mode: xml ***
./runtime_control.xml:691:     ;;; mode: xml ***
./intro.xml:304:     ;;; mode: xml ***
./installing.xml:529:     ;;; mode: xml ***
./ffi-chap.xml:523:     ;;; mode: xml ***
./sooner.xml:542:     ;;; mode: xml ***
./parallel.xml:176:     ;;; mode: xml ***
./profiling.xml:1713:     ;;; mode: xml ***
./ug-book.xml:28:     ;;; mode: xml ***
./phases.xml:1071:     ;;; mode: xml ***
./gone_wrong.xml:210:     ;;; mode: xml ***

Of these, probably only the one in ug-book.xml.in is actually useful, since that file doesn't have a name ending in .xml.

Trac metadata
Trac field Value
Version 6.9
Type Bug
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component Documentation
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system Unknown
Architecture Unknown
\r\n}}}\r\n\r\nThe \"mode:\" line, in particular (assuming the user hasn't disabled the feature) overrides the user's choice of mode for XML editing (when the filename ends in .xml or another common XML suffix, anyway). Since I use {{{nxml-mode}}}, not {{{xml-mode}}}, this bothers me.\r\n\r\nA quick grep turns up:\r\n{{{\r\ncd /home/naesten/hacking/haskell/ghc-hashedrepo/docs/users_guide/\r\ngrep -n -e 'mode: xml' --recursive . /dev/null\r\n./runghc.xml:39: ;;; mode: xml ***\r\n./packages.xml:1271: ;;; mode: xml ***\r\n./5-00-notes.xml:204: ;;; mode: xml ***\r\n./using.xml:1848: ;;; mode: xml ***\r\n./utils.xml:561: ;;; mode: xml ***\r\n./glasgow_exts.xml:7546: ;;; mode: xml ***\r\n./license.xml:63: ;;; mode: xml ***\r\n./ug-book.xml.in:28: ;;; mode: xml ***\r\n./bugs.xml:404: ;;; mode: xml ***\r\n./6.0-notes.xml:316: ;;; mode: xml ***\r\n./debugging.xml:624: ;;; mode: xml ***\r\n./5-04-notes.xml:285: ;;; mode: xml ***\r\n./win32-dlls.xml:633: ;;; mode: xml ***\r\n./5-02-notes.xml:54: ;;; mode: xml ***\r\n./ghci.xml:2827: ;;; mode: xml ***\r\n./flags.xml:2341: ;;; mode: xml ***\r\n./lang.xml:12: ;;; mode: xml ***\r\n./separate_compilation.xml:1261: ;;; mode: xml ***\r\n./runtime_control.xml:691: ;;; mode: xml ***\r\n./intro.xml:304: ;;; mode: xml ***\r\n./installing.xml:529: ;;; mode: xml ***\r\n./ffi-chap.xml:523: ;;; mode: xml ***\r\n./sooner.xml:542: ;;; mode: xml ***\r\n./parallel.xml:176: ;;; mode: xml ***\r\n./profiling.xml:1713: ;;; mode: xml ***\r\n./ug-book.xml:28: ;;; mode: xml ***\r\n./phases.xml:1071: ;;; mode: xml ***\r\n./gone_wrong.xml:210: ;;; mode: xml ***\r\n}}}\r\n\r\nOf these, probably only the one in {{{ug-book.xml.in}}} is actually useful, since that file doesn't have a name ending in .xml.","type_of_failure":"OtherFailure","blocking":[]} -->
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information