unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: mattiase@acm.org, emacs-devel@gnu.org
Subject: RE: [PATCH] Replace latin-1-specific case-manipulation
Date: Thu, 21 Feb 2019 07:23:57 -0800 (PST)	[thread overview]
Message-ID: <3c868f5a-0920-491a-8318-45e98b4ac576@default> (raw)
In-Reply-To: <<834l8xgqbx.fsf@gnu.org>>

> > > I think it's simply because Emacs didn't have
> > > 'capitalize' back then.  That code survived
> > > since 1990.  So of course it's OK to use
> > > capitalize now.
> >
> > FWIW, I think I used `capitalize', `capitalize-word',
> > and `capitalize-region' long ago, in the mid 1980s.
> 
> In what program?  Emacs was first released "in mid 1980s", did you use
> Emacs before version 18.

GNU Emacs, from the outset of my use of it.

But I don't know if it was before v18.  (I
definitely used v18.)

And I could be mistaken.  My recollection is
using capitalization commands as soon as GNU
Emacs was available (to me), in the 1980s.

My doubt is that this was introduced only in
1990 - but I could be wrong.

In any case, if there's no reason for this
code not to use `capitalize' then use
`capitalize'.  I wouldn't think that that
decision should depend on when `capitalize'
was first introduced.

> > I could be mistaken, but my recollection is that
> > at least commands like `capitalize-word' and
> > `upcase-word' were used back then.
> 
> For ASCII, most probably.

Yes, probably.  Some non-ASCII latin-1 too,
but I may have used such commands only with
ASCII.



       reply	other threads:[~2019-02-21 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<23807310-A2F9-4322-8A2C-03A63EFFD2AE@acm.org>
     [not found] ` <<83va1egypa.fsf@gnu.org>
     [not found]   ` <<779A26F9-FE8F-477E-81BD-86200977E81D@acm.org>
     [not found]     ` <<83ef81hkwb.fsf@gnu.org>
     [not found]       ` <<b5545b1f-2488-4943-a063-09c25ace7b9b@default>
     [not found]         ` <<834l8xgqbx.fsf@gnu.org>
2019-02-21 15:23           ` Drew Adams [this message]
2019-02-20 14:26 [PATCH] Replace latin-1-specific case-manipulation Mattias Engdegård
2019-02-20 17:24 ` Eli Zaretskii
2019-02-20 20:47   ` Mattias Engdegård
2019-02-21  3:37     ` Eli Zaretskii
2019-02-21  5:25       ` Drew Adams
2019-02-21 14:37         ` Eli Zaretskii
2019-02-21  9:30       ` Mattias Engdegård

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3c868f5a-0920-491a-8318-45e98b4ac576@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.org \
    /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 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).