unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ralf Angeli <dev.null@caeruleus.net>
To: help-gnu-emacs@gnu.org
Subject: Re: How to redefine Parantheses?
Date: Mon, 09 Apr 2007 19:37:36 +0200	[thread overview]
Message-ID: <461a79e0$0$20296$9b4e6d93@newsspool3.arcor-online.net> (raw)
In-Reply-To: mailman.1877.1176139102.7795.help-gnu-emacs@gnu.org

* Eli Zaretskii (2007-04-09) writes:

>> From: Ralf Angeli <dev.null@caeruleus.net>
>> Date: Mon, 09 Apr 2007 10:58:35 +0200
>> 
>> I really don't understand why the default syntax in Emacs is paren
>> syntax.
>
> Because Emacs currently cannot distinguish between different usage of
> the same character in different languages, and even your research
> indicates that the current behavior is correct in 50% of cases.
>
>> But I don't think is a customization issue but a bug in Emacs.
>
> Not a bug, a missing feature.

Even with that feature missing one could get 100% correct behavior by
giving guillemets punctuation syntax.  You may give the problem a
different name, but changing the default syntax is ceteris paribus
still the better option.

-- 
Ralf

  parent reply	other threads:[~2007-04-09 17:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-08  7:19 How to redefine Parantheses? Paul Batt
2007-04-08  8:16 ` Eli Zaretskii
     [not found] ` <mailman.1835.1176020435.7795.help-gnu-emacs@gnu.org>
2007-04-08  9:35   ` Ralf Angeli
2007-04-08 21:05     ` Eli Zaretskii
     [not found]     ` <mailman.1844.1176066558.7795.help-gnu-emacs@gnu.org>
2007-04-08 21:15       ` Ralf Angeli
2007-04-09  5:56         ` Eli Zaretskii
2007-04-09  6:22           ` David Hansen
     [not found]           ` <mailman.1849.1176100080.7795.help-gnu-emacs@gnu.org>
2007-04-09  9:20             ` Ralf Angeli
     [not found]         ` <mailman.1848.1176098439.7795.help-gnu-emacs@gnu.org>
2007-04-09  8:58           ` Ralf Angeli
2007-04-09 15:14             ` Eli Zaretskii
     [not found]             ` <mailman.1877.1176139102.7795.help-gnu-emacs@gnu.org>
2007-04-09 17:37               ` Ralf Angeli [this message]
2007-04-10  3:10                 ` Eli Zaretskii
     [not found]                 ` <mailman.1897.1176174905.7795.help-gnu-emacs@gnu.org>
2007-04-10 17:35                   ` Ralf Angeli
2007-04-10 19:23                     ` Eli Zaretskii
     [not found]                     ` <mailman.1921.1176233276.7795.help-gnu-emacs@gnu.org>
2007-04-10 19:50                       ` Ralf Angeli
2007-04-11  3:34                         ` Eli Zaretskii
     [not found]                         ` <mailman.1934.1176262700.7795.help-gnu-emacs@gnu.org>
2007-04-11 16:53                           ` Ralf Angeli
2007-04-11 18:42                             ` Eli Zaretskii
2007-04-09 16:48   ` Paul Batt
2007-04-09 18:27     ` Eli Zaretskii
     [not found]     ` <mailman.1882.1176143496.7795.help-gnu-emacs@gnu.org>
2007-04-10  6:36       ` Paul Batt
2007-04-10 17:42         ` Ralf Angeli
2007-04-10 18:21           ` Paul Batt
2007-04-10 18:52         ` Eli Zaretskii
     [not found]         ` <mailman.1919.1176231393.7795.help-gnu-emacs@gnu.org>
2007-04-11 10:46           ` Paul Batt
2007-04-08 11:14 ` Peter Dyballa

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='461a79e0$0$20296$9b4e6d93@newsspool3.arcor-online.net' \
    --to=dev.null@caeruleus.net \
    --cc=angeli@caeruleus.net \
    --cc=help-gnu-emacs@gnu.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.
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).