unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: schwab@suse.de, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: Word syntax question
Date: Wed, 22 Oct 2008 21:21:38 +0200	[thread overview]
Message-ID: <uy70ge8ql.fsf@gnu.org> (raw)
In-Reply-To: <E1KsX5I-0002wE-3s@fencepost.gnu.org>

> From: "Richard M. Stallman" <rms@gnu.org>
> CC: miles@gnu.org, schwab@suse.de, emacs-devel@gnu.org
> Date: Wed, 22 Oct 2008 02:20:44 -0400
> 
>     I agree.  I think we should introduce a user option to control whether
>     it stops on script boundaries or not, because sometimes it makes
>     sense, sometimes it doesn't.
> 
> That is not a real solution.  The right thing to do is a function
> of the case, not the user.  Making each user specify an option
> according to which cases she typically encounters is not clean.

I agree that it would be better to solve this automatically, but I
sincerely doubt that we will get that right in time for the release
(unless we delay the release for many months).

> It seems that we need a way to specify which kinds of script
> boundaries should be word boundaries, on designed to produce the
> results that users generally want, and which could be set up inside
> Emacs so that users don't have to change it.

I think we lack the knowledge for doing this right.  We don't even
have enough experts on board to cover all the Unicode scripts, or even
their majority.  How in the world will we decide which scripts can or
cannot be mixed in the same word, let alone how this might change in
some specialized Emacs mode?  Unicode annexes know nothing about many
Emacs features, so their advice will not help us except maybe in Text
mode and its closest derivatives.  We will need to develop our own
solutions as we go, like we did with syntax tables in previous
versions, for example.

However, developing those solutions might take a lot of time and user
experience which we do not yet have.  It will take a lot of effort
just to solve the bugs and sluggish performance to bring Emacs 23 to a
releasable state, so if on top of that we delay the release until this
and similar Unicode-related issues are satisfactorily resolved, we
will not release Emacs 23 before another 2 or 3 years pass by.

With that in mind, my suggestion to provide a user option was meant to
give users a fire escape in case Emacs 23.1 does not get their
use-case right.




  reply	other threads:[~2008-10-22 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 15:20 Word syntax question Miles Bader
2008-10-21 15:52 ` Andreas Schwab
2008-10-21 16:35   ` Miles Bader
2008-10-21 17:21     ` Eli Zaretskii
2008-10-22  0:58       ` Miles Bader
2008-10-22  3:11         ` Stephen J. Turnbull
2008-10-22 11:52           ` Kenichi Handa
2008-10-22 12:23           ` Kenichi Handa
2008-10-22  4:29         ` Eli Zaretskii
2008-10-22  5:16           ` Miles Bader
2008-10-22 19:36             ` Eli Zaretskii
2008-10-22 21:02           ` Richard M. Stallman
2008-10-22  6:20       ` Richard M. Stallman
2008-10-22 19:21         ` Eli Zaretskii [this message]
2008-10-23  3:09           ` Richard M. Stallman

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=uy70ge8ql.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=rms@gnu.org \
    --cc=schwab@suse.de \
    /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).