5:37 a.m.
Dear XEmacs devellopers,
I have a question about my IDLWAVE package. Some time ago (1.5years?)
I submitted a patch to files.el (auto-mode-alist) which would turn on
IDLWAVE mode automatically for files with the extension ".pro". This
patch started a discussion if auto-mode-alist entries related to
packages should be in files.el or if they should be installed
dynamically by the autoload forms in package. I don't know what the
outcome of this discussion was (I don't read the develloper mailing
lists), but the result is that my package is not automatically used
for ".pro" files and user have to install autoload forms by hand.
This is not the way it should be. Could someone please decide what
the policy about this is, so that I can make a patch to either
files.el (adding an entry to auto-mode-alist) or to IDLWAVE (adding an
autoload form which does
(setq auto-mode-alist (cons ("\.[Pp][Rr][Oo]\\'" . idlwave-mode)
auto-mode-alist))
- Carsten
PS. Please CC me on replies. Thanks!
--
Carsten Dominik <dominik(a)astro.uva.nl> \ _ /
Sterrenkundig Instituut "Anton Pannekoek" |X| _
Kruislaan 403; NL-1098 SJ Amsterdam /| |\ _ _ _/ \
phone +31 (20) 525-7477; FAX +31 (20) 525-7484 __|o|___/ ~~ \___/ ~~~
8:36 a.m.
New subject: Package Release
Carsten Dominik <dominik(a)astro.uva.nl> writes:
Could someone please decide what
the policy about this is, so that I can make a patch to either
files.el (adding an entry to auto-mode-alist) or to IDLWAVE (adding an
autoload form which does
(setq auto-mode-alist (cons ("\.[Pp][Rr][Oo]\\'" . idlwave-mode)
auto-mode-alist))
I'm not speaking for the project, but IMO it is OK to add an
entry to auto-mode-alist. There already exist bunch of
package dependent entries. I don't think an error produced
when opening .pro file without idlwave package is too
annoying. Besides, auto-mode-alist has .idl entry. It does
no harm to add another entry for idlwave-mode.
--
Yoshiki Hayashi
9:11 a.m.
New subject: Package Release
>>>> "Y" == Yoshiki Hayashi
<yoshiki(a)xemacs.org> writes:
Y> Carsten Dominik <dominik(a)astro.uva.nl> writes:
> Could someone please decide what
> the policy about this is, so that I can make a patch to either
> files.el (adding an entry to auto-mode-alist) or to IDLWAVE (adding an
> autoload form which does
>
> (setq auto-mode-alist (cons ("\.[Pp][Rr][Oo]\\'" . idlwave-mode)
> auto-mode-alist))
Y> I'm not speaking for the project, but IMO it is OK to add an
Y> entry to auto-mode-alist. There already exist bunch of
Y> package dependent entries. I don't think an error produced
Y> when opening .pro file without idlwave package is too
Y> annoying. Besides, auto-mode-alist has .idl entry. It does
Y> no harm to add another entry for idlwave-mode.
I still think there are better architected ways to do this, but we can
pontificate forever, so let's just add Carsten's entry to the global
variable for now. Yoshiki, could you take care of this?
Martin
10:53 a.m.
New subject: Package Release
Martin Buchholz <martin(a)xemacs.org> writes:
I still think there are better architected ways to do this, but we
can
pontificate forever, so let's just add Carsten's entry to the global
variable for now. Yoshiki, could you take care of this?
Oops. Stephen is right. Andreas already applied Carsten's
patch to XEmacs 21.2. And I also made mistake about .idl
suffix. Perhaps I was tired after taking a boring
class... :-) Here's the patch to change it to the version he
posted.
2000-10-25 Yoshiki Hayashi <yoshiki(a)xemacs.org>
* files.el (auto-mode-alist): Allow mixed case suffix for idlwave-mode.
Index: files.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/files.el,v
retrieving revision 1.27.2.27
diff -u -r1.27.2.27 files.el
--- files.el 2000/10/18 12:24:56 1.27.2.27
+++ files.el 2000/10/25 09:44:04
＠＠ -1173,7 +1173,7 ＠＠
("\\.m\\(?:[mes]\\|an\\)\\'" . nroff-mode)
("\\.icn\\'" . icon-mode)
("\\.\\(?:[ckz]?sh\\|shar\\)\\'" . sh-mode)
- ("\\.pro\\'" . idlwave-mode)
+ ("\\.[Pp][Rr][Oo]\\'" . idlwave-mode)
;; #### Unix-specific!
("/\\.\\(?:bash_\\|z\\)?\\(profile\\|login\\|logout\\)\\'" . sh-mode)
("/\\.\\(?:[ckz]sh\\|bash\\|tcsh\\|es\\|xinit\\|startx\\)rc\\'" .
sh-mode)
--
Yoshiki Hayashi
9:34 a.m.
New subject: Package Release
>>>> "Carsten" == Carsten Dominik
<dominik(a)astro.uva.nl> writes:
Carsten> I have a question about my IDLWAVE package. Some time
Carsten> ago (1.5years?) I submitted a patch to files.el
Carsten> (auto-mode-alist) which would turn on IDLWAVE mode
Carsten> automatically for files with the extension ".pro".
The patch is already in 21.2.x, but not yet in 21.1.x.
I think this is _wrong_, but since that alist is already way out of
hand, I don't see anything horrible about adding it to 21.1, too.
This is Vin Shelton's area, though, since it's 21.1.
Carsten> This is not the way it should be.
This _is_ the way it _should_ be.[1] I setq auto-mode-alist to a
literal list in .emacs because I'm sick of being surprised at the mode
that Emacs decides on, and worse, having it change after an update.
Until the popularity of SUMOs dies out, which I don't think will
happen, we just will have too many packages adding too many
extensions. We already have several conflicts noted in the source
code, and only one can win. ".pro" strikes me as a very likely
candidate for conflicts of that kind; at least ".idl" seems pretty
specific to IDL.
Carsten> (setq auto-mode-alist (cons ("\.[Pp][Rr][Oo]\\'" .
idlwave-mode)
Carsten> auto-mode-alist))
Please, do not do it this way. Make the change in files.el, until we
have a standard way to handle it in the package.
Footnotes:
[1] But first we should find a way to deal with this constructively
(offhand a hook in package installation which checks for the package's
auto-modes, and offers to install them, seems like the way to go).
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
11:16 a.m.
New subject: [21.1] Update auto-mode-alist (was Re: Package Release)
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
The patch is already in 21.2.x, but not yet in 21.1.x.
I think this is _wrong_, but since that alist is already way out of
hand, I don't see anything horrible about adding it to 21.1, too.
This is Vin Shelton's area, though, since it's 21.1.
Here's the patch to sync auto-mode-alist to 21.2.
I think it's pretty safe, but it's up to Vin whether this
patch is applied or not.
I really agree there should be a better way to handle this.
I sometimes wish I could blow up current package system and
introduce Scheme48 (or librep) like module system to XEmacs.
2000-10-25 Yoshiki Hayashi <yoshiki(a)xemacs.org>
* files.el (auto-mode-alist): Update to 21.2 version.
Index: files.el
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/files.el,v
retrieving revision 1.37
diff -u -r1.37 files.el
--- files.el 2000/07/31 00:33:12 1.37
+++ files.el 2000/10/25 10:08:59
＠＠ -1159,51 +1159,53 ＠＠
(defvar auto-mode-alist
'(("\\.te?xt\\'" . text-mode)
- ("\\.[ch]\\'" . c-mode)
+ ("\\.[chi]\\'" . c-mode)
("\\.el\\'" . emacs-lisp-mode)
- ("\\.\\([CH]\\|cc\\|hh\\)\\'" . c++-mode)
+ ("\\.\\(?:[CH]\\|cc\\|hh\\)\\'" . c++-mode)
("\\.[ch]\\(pp\\|xx\\|\\+\\+\\)\\'" . c++-mode)
("\\.java\\'" . java-mode)
("\\.idl\\'" . idl-mode)
- ("\\.f\\(or\\)?\\'" . fortran-mode)
- ("\\.F\\(OR\\)?\\'" . fortran-mode)
+ ("\\.f\\(?:or\\)?\\'" . fortran-mode)
+ ("\\.F\\(?:OR\\)?\\'" . fortran-mode)
("\\.[fF]90\\'" . f90-mode)
;;; Less common extensions come here
;;; so more common ones above are found faster.
("\\.\\([pP][Llm]\\|al\\)\\'" . perl-mode)
("\\.py\\'" . python-mode)
- ("\\.texi\\(nfo\\)?\\'" . texinfo-mode)
+ ("\\.texi\\(?:nfo\\)?\\'" . texinfo-mode)
("\\.ad[abs]\\'" . ada-mode)
- ("\\.c?l\\(i?sp\\)?\\'" . lisp-mode)
- ("\\.p\\(as\\)?\\'" . pascal-mode)
+ ("\\.c?l\\(?:i?sp\\)?\\'" . lisp-mode)
+ ("\\.p\\(?:as\\)?\\'" . pascal-mode)
("\\.ltx\\'" . latex-mode)
("\\.[sS]\\'" . asm-mode)
- ("[Cc]hange.?[Ll]og?\\(.[0-9]+\\)?\\'" . change-log-mode)
+ ("[Cc]hange.?[Ll]og?\\(?:.[0-9]+\\)?\\'" . change-log-mode)
("\\$CHANGE_LOG\\$\\.TXT" . change-log-mode)
("\\.scm?\\(?:\\.[0-9]*\\)?\\'" . scheme-mode)
("\\.e\\'" . eiffel-mode)
("\\.mss\\'" . scribe-mode)
- ("\\.m\\([mes]\\|an\\)\\'" . nroff-mode)
+ ("\\.m\\(?:[mes]\\|an\\)\\'" . nroff-mode)
("\\.icn\\'" . icon-mode)
- ("\\.\\([ckz]?sh\\|shar\\)\\'" . sh-mode)
+ ("\\.\\(?:[ckz]?sh\\|shar\\)\\'" . sh-mode)
+ ("\\.[Pp][Rr][Oo]\\'" . idlwave-mode)
;; #### Unix-specific!
- ("/\\.\\(bash_\\|z\\)?\\(profile\\|login\\|logout\\)\\'" . sh-mode)
- ("/\\.\\([ckz]sh\\|bash\\|tcsh\\|es\\|xinit\\|startx\\)rc\\'" .
sh-mode)
- ("/\\.\\([kz]shenv\\|xsession\\)\\'" . sh-mode)
+ ("/\\.\\(?:bash_\\|z\\)?\\(profile\\|login\\|logout\\)\\'" . sh-mode)
+ ("/\\.\\(?:[ckz]sh\\|bash\\|tcsh\\|es\\|xinit\\|startx\\)rc\\'" .
sh-mode)
+ ("/\\.\\(?:[kz]shenv\\|xsession\\)\\'" . sh-mode)
+ ("\\.m?spec$" .sh-mode)
;; The following come after the ChangeLog pattern for the sake of
;; ChangeLog.1, etc. and after the .scm.[0-9] pattern too.
("\\.[12345678]\\'" . nroff-mode)
("\\.[tT]e[xX]\\'" . tex-mode)
- ("\\.\\(sty\\|cls\\|bbl\\)\\'" . latex-mode)
+ ("\\.\\(?:sty\\|cls\\|bbl\\)\\'" . latex-mode)
("\\.bib\\'" . bibtex-mode)
("\\.article\\'" . text-mode)
("\\.letter\\'" . text-mode)
- ("\\.\\(tcl\\|exp\\)\\'" . tcl-mode)
+ ("\\.\\(?:tcl\\|exp\\)\\'" . tcl-mode)
("\\.wrl\\'" . vrml-mode)
("\\.awk\\'" . awk-mode)
("\\.prolog\\'" . prolog-mode)
("\\.tar\\'" . tar-mode)
- ("\\.\\(arc\\|zip\\|lzh\\|zoo\\)\\'" . archive-mode)
+ ("\\.\\(?:arc\\|zip\\|lzh\\|zoo\\)\\'" . archive-mode)
;; Mailer puts message to be edited in /tmp/Re.... or Message
;; #### Unix-specific!
("\\`/tmp/Re" . text-mode)
＠＠ -1215,9 +1217,10 ＠＠
("\\.lex\\'" . c-mode)
("\\.m\\'" . objc-mode)
("\\.oak\\'" . scheme-mode)
- ("\\.s?html?\\'" . html-mode)
- ("\\.htm?l?3\\'" . html3-mode)
- ("\\.\\(sgml?\\|dtd\\)\\'" . sgml-mode)
+ ("\\.[sj]?html?\\'" . html-mode)
+ ("\\.jsp\\'" . html-mode)
+ ("\\.xml\\'" . xml-mode)
+ ("\\.\\(?:sgml?\\|dtd\\)\\'" . sgml-mode)
("\\.c?ps\\'" . postscript-mode)
;; .emacs following a directory delimiter in either Unix or
;; Windows syntax.
＠＠ -1225,16 +1228,16 ＠＠
("\\.m4\\'" . autoconf-mode)
("configure\\.in\\'" . autoconf-mode)
("\\.ml\\'" . lisp-mode)
- ("\\.ma?k\\'" . makefile-mode)
+ ("\\.ma?ke?\\'" . makefile-mode)
("[Mm]akefile\\(\\.\\|\\'\\)" . makefile-mode)
("\\.X\\(defaults\\|environment\\|resources\\|modmap\\)\\'" .
xrdb-mode)
;; #### The following three are Unix-specific (but do we care?)
("/app-defaults/" . xrdb-mode)
- ("\\.[^/]*wm\\'" . winmgr-mode)
- ("\\.[^/]*wm2?rc" . winmgr-mode)
+ ("\\.[^/]*wm2?\\(?:rc\\)?\\'" . winmgr-mode)
("\\.[Jj][Pp][Ee]?[Gg]\\'" . image-mode)
("\\.[Pp][Nn][Gg]\\'" . image-mode)
("\\.[Gg][Ii][Ff]\\'" . image-mode)
+ ("\\.[Tt][Ii][Ff][Ff]?\\'" . image-mode)
)
"Alist of filename patterns vs. corresponding major mode functions.
Each element looks like (REGEXP . FUNCTION) or (REGEXP FUNCTION NON-NIL).
--
Yoshiki Hayashi
8794
days inactive
8794
days old
5 comments
4 participants
participants (4)
-
Carsten Dominik -
Martin Buchholz -
Stephen J. Turnbull -
Yoshiki Hayashi