From: Alex Kost <alezost@gmail.com>
To: Ivan Vilata i Balaguer <ivan@selidor.net>
Cc: 24442@debbugs.gnu.org
Subject: bug#24442: gettext: No PO mode for Emacs (or wrong description)
Date: Thu, 29 Sep 2016 11:03:41 +0300 [thread overview]
Message-ID: <8760pfjfoi.fsf@gmail.com> (raw)
In-Reply-To: <20160915070426.GI5711@sax.terramar.selidor.net> (Ivan Vilata i. Balaguer's message of "Thu, 15 Sep 2016 09:04:26 +0200")
Ivan Vilata i Balaguer (2016-09-15 09:04 +0200) wrote:
> The description for ``gettext@0.19.8`` (current) includes this sentence:
>
> It provides translators with the means to create message catalogs,
> as well as an Emacs mode to work with them, and a runtime library to
> load translated messages from the catalogs.
>
> However, no output of the package includes the files for Emacs.
This is fixed in 'core-updates' branch now:
<http://git.savannah.gnu.org/cgit/guix.git/commit/?id=9e01589469abd89e035450d29026f0e14add6801>,
however since the fix is not available for users (until core-updates
will be merged into master) I think it's better to leave this bug
opened.
Once the fix appears in 'master' (I will let you know when it happens),
a user could do "guix pull" and install (or update) 'gettext' in his/her
profile. Then 'po-mode' will become available by default (without any
additional settings in user's .emacs), it means that whenever you will
open .po file, 'po-mode' will be loaded and enabled automatically.
--
Alex
next prev parent reply other threads:[~2016-09-29 8:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 7:04 bug#24442: gettext: No PO mode for Emacs (or wrong description) Ivan Vilata i Balaguer
2016-09-19 8:58 ` Alex Kost
2016-09-24 1:55 ` Ludovic Courtès
2016-09-25 8:09 ` Alex Kost
2016-09-29 8:03 ` Alex Kost [this message]
2016-09-29 11:15 ` Ivan Vilata i Balaguer
2016-11-17 14:56 ` Ivan Vilata i Balaguer
2016-11-18 9:36 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760pfjfoi.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=24442@debbugs.gnu.org \
--cc=ivan@selidor.net \
/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/guix.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).