unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rahguzar <rahguzar@zohomail.eu>
Cc: 66470@debbugs.gnu.org
Subject: bug#66470: 29.1; Provide Urdu input method
Date: Sat, 14 Oct 2023 15:36:16 +0300	[thread overview]
Message-ID: <83sf6dqt33.fsf@gnu.org> (raw)
In-Reply-To: <8734yd1mfm.fsf@zohomail.eu> (message from Rahguzar on Sat, 14 Oct 2023 13:10:36 +0200)

> From: Rahguzar <rahguzar@zohomail.eu>
> Cc: 66470@debbugs.gnu.org
> Date: Sat, 14 Oct 2023 13:10:36 +0200
> 
> Another question: will the input methods be available in 29.2 if added
> in time or in Emacs 30?

In general, Emacs 30 is a more practical goal, although if you succeed
to do this quickly enough, we could also consider adding this to Emacs
29.2.  But (barring any unforeseen problems) Emacs 29.2 should be out
fairly soon-ish, so I wouldn't recommend trying to rush with these
changes just to be ready in time.





  reply	other threads:[~2023-10-14 12:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 18:36 bug#66470: 29.1; Provide Urdu input method Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-11 18:50 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14  8:53   ` Eli Zaretskii
2023-10-14  9:50     ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 10:53       ` Eli Zaretskii
2023-10-14 11:10         ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-14 12:36           ` Eli Zaretskii [this message]
2023-10-21 18:59             ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-22  4:53               ` Eli Zaretskii
2023-10-29 11:51               ` Eli Zaretskii
2023-10-29 16:27                 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04  8:39                   ` Eli Zaretskii
2023-11-04  8:50                     ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04  9:27                       ` Eli Zaretskii
2023-11-04 10:56                         ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 11:15                           ` Eli Zaretskii
2023-11-04 14:23                             ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-11 10:21                               ` Eli Zaretskii
2023-11-11 11:54                                 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-18  9:36                                   ` Eli Zaretskii
2023-11-18 11:12                                     ` Rahguzar 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=83sf6dqt33.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66470@debbugs.gnu.org \
    --cc=rahguzar@zohomail.eu \
    /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).