* coding problem, with older GNU emacs or Xemacs; auto-capitalize.el
@ 2016-04-16 8:33 Uwe Brauer
2016-04-16 9:12 ` Eli Zaretskii
0 siblings, 1 reply; 3+ messages in thread
From: Uwe Brauer @ 2016-04-16 8:33 UTC (permalink / raw)
To: emacs-devel; +Cc: XEmacs Beta Discussion
Hello
the nifty but not much used auto-capitalize.el had a bug in buffers
which are using AUCTeX Latex mode. That bug has been fixed thanks to
Mosè Mosè, but the original code is in emacs wiki and contains some
strange coding and lines
- it starts with
;;; auto-capitalize.el --- Automatically capitalize (or upcase) words
;;; -*-unibyte: t; coding: iso-8859-1;-*-
;; Copyright � 1998,2001,2002,2005 Kevin Rodgers
What would be an more appropriate coding (which should work in GNU emacs,
Xemacs (including Xemacs no mule)?
- more worrying are these lines
(if (featurep 'xemacs)
"\\<\\([A-Z�-��-�]?[a-z�-��-�]+\\.\\)+\\="
"\\<\\([[:upper:]]?[[:lower:]]+\\.\\)+\\=")))
I am not sure they will be sent correctly.
That seems much more an Xemacs issue than GNU emacs. I just want to make
sure what will be the best choice for the coding so that the code keeps
working for newer/older versions of GNU emacs and Xemacs (Mule and no
Mule).
Any advice is appreciated.
thanks
Uwe Brauer
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: coding problem, with older GNU emacs or Xemacs; auto-capitalize.el
2016-04-16 8:33 coding problem, with older GNU emacs or Xemacs; auto-capitalize.el Uwe Brauer
@ 2016-04-16 9:12 ` Eli Zaretskii
2016-04-16 17:53 ` Uwe Brauer
0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2016-04-16 9:12 UTC (permalink / raw)
To: Uwe Brauer; +Cc: emacs-devel
> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Sat, 16 Apr 2016 08:33:07 +0000
> Cc: XEmacs Beta Discussion <xemacs-beta@xemacs.org>
>
> the nifty but not much used auto-capitalize.el had a bug in buffers
> which are using AUCTeX Latex mode. That bug has been fixed thanks to
> Mosè Mosè, but the original code is in emacs wiki and contains some
> strange coding and lines
>
> - it starts with
> ;;; auto-capitalize.el --- Automatically capitalize (or upcase) words
> ;;; -*-unibyte: t; coding: iso-8859-1;-*-
> ;; Copyright � 1998,2001,2002,2005 Kevin Rodgers
For Emacs, just remove all that stuff, it's unnecessary.
> What would be an more appropriate coding (which should work in GNU emacs,
> Xemacs (including Xemacs no mule)?
I have no idea how XEmacs works wrt this, so no comment here.
> - more worrying are these lines
>
> (if (featurep 'xemacs)
> "\\<\\([A-Z�-��-�]?[a-z�-��-�]+\\.\\)+\\="
> "\\<\\([[:upper:]]?[[:lower:]]+\\.\\)+\\=")))
Once again, the funny stuff is only for XEmacs, so I think you are
asking in the wrong place. The Emacs branch of this is clear, and
doesn't need any encoding-related tricks.
> That seems much more an Xemacs issue than GNU emacs. I just want to make
> sure what will be the best choice for the coding so that the code keeps
> working for newer/older versions of GNU emacs and Xemacs (Mule and no
> Mule).
I think you should ask on the XEmacs list, not here.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: coding problem, with older GNU emacs or Xemacs; auto-capitalize.el
2016-04-16 9:12 ` Eli Zaretskii
@ 2016-04-16 17:53 ` Uwe Brauer
0 siblings, 0 replies; 3+ messages in thread
From: Uwe Brauer @ 2016-04-16 17:53 UTC (permalink / raw)
To: emacs-devel
> For Emacs, just remove all that stuff, it's unnecessary.
Thanks.
> I think you should ask on the XEmacs list, not here.
That is why I have CCed to Xemacs beta :-D
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-04-16 17:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-16 8:33 coding problem, with older GNU emacs or Xemacs; auto-capitalize.el Uwe Brauer
2016-04-16 9:12 ` Eli Zaretskii
2016-04-16 17:53 ` Uwe Brauer
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).