From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: coding problem, with older GNU emacs or Xemacs; auto-capitalize.el
Date: Sat, 16 Apr 2016 12:12:33 +0300 [thread overview]
Message-ID: <838u0ddiim.fsf@gnu.org> (raw)
In-Reply-To: <878u0ear7g.fsf@mat.ucm.es> (message from Uwe Brauer on Sat, 16 Apr 2016 08:33:07 +0000)
> 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.
next prev parent reply other threads:[~2016-04-16 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2016-04-16 17:53 ` Uwe Brauer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838u0ddiim.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.