unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thanos Apollo <public@thanosapollo.org>
Cc: 73909-done@debbugs.gnu.org
Subject: bug#73909: [PATCH 2/2] quail/greek.el: Add greek-polytonic.
Date: Sun, 03 Nov 2024 09:26:45 +0200	[thread overview]
Message-ID: <86o72wwzey.fsf@gnu.org> (raw)
In-Reply-To: <87o72wssiu.fsf@thanosapollo.org> (message from Thanos Apollo on Sun, 03 Nov 2024 09:09:13 +0200)

> From: Thanos Apollo <public@thanosapollo.org>
> Cc: 73909@debbugs.gnu.org
> Date: Sun, 03 Nov 2024 09:09:13 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> [...]
> >
> > This part is AFAICT new in the patch, it was never discussed before.
> > It's okay to add more sequences for « and », but can you tell why we
> > should remove the old sequences? do they get in the way or something?
> > If the old sequences don't do any harm, I'd prefer to keep them _and_
> > add the new ones.
> 
> True, keeping the current bindings & just adding extra ones is a better
> option.  Note that "greek-postfix" uses "<<" & ">>" for double angle
> quotation markings as well, not ";<", this addition makes the greek
> input methods more "coherent" with each other.
> 
> Attaching patches below, after having done a rebase on master.

Thanks, installed on master, and closing the bug.





  reply	other threads:[~2024-11-03  7:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-20 12:46 bug#73909: [PATCH 2/2] quail/greek.el: Add greek-polytonic Thanos Apollo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-20 13:13 ` Eli Zaretskii
2024-10-20 13:21   ` Thanos Apollo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-20 13:54     ` Eli Zaretskii
2024-11-02 10:58       ` Thanos Apollo
2024-11-02 11:38       ` Eli Zaretskii
2024-11-03  3:57         ` Thanos Apollo
2024-11-03  6:50           ` Eli Zaretskii
2024-11-03  7:09             ` Thanos Apollo
2024-11-03  7:26               ` Eli Zaretskii [this message]
2024-11-03  8:43                 ` Thanos Apollo
2024-11-03  8:54                   ` bug#73908: " Eli Zaretskii
2024-10-20 18:07 ` Visuwesh
2024-10-20 18:10   ` Visuwesh
2024-10-20 19:35   ` Thanos Apollo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-21 10:45     ` Robert Pluim
2024-10-21 11:05       ` Visuwesh
2024-10-21 13:36         ` Robert Pluim
2024-10-21 13:53           ` Visuwesh
2024-10-21 14:18             ` Robert Pluim
2024-10-21 14:31               ` Visuwesh
2024-10-21 14:45                 ` Robert Pluim
2024-10-21 15:06                   ` Visuwesh
2024-10-21 12:57       ` Thanos Apollo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-21 13:30         ` Robert Pluim
2024-10-21 13:39           ` Robert Pluim
2024-10-21 15:43             ` Thanos Apollo via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86o72wwzey.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73909-done@debbugs.gnu.org \
    --cc=public@thanosapollo.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).