From: Deus Max <deusmax@gmx.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 39026@debbugs.gnu.org
Subject: bug#39026: 27.0.50; gnus-group-decoded-name needs running gnus
Date: Mon, 13 Jan 2020 22:57:06 +0200 [thread overview]
Message-ID: <874kwz6pnh.fsf@aia00054aia.gr> (raw)
In-Reply-To: <87woa1bw9q.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 08 Jan 2020 11:09:21 -0800")
On Mon, Jan 13 2020, Eric Abrahamsen wrote:
>
> Yeah, to be honest, I don't really know the point of the
> gnus-group-name-charset-* stuff, and am mostly unwilling to mess with
> anything I don't really understand. But if those variables have been
> set, we'd need to know a group's method, and it really isn't possible to
> get a group's method for sure unless Gnus is up and running.
>
> In fact, I suspect we could simply dump all the group-name-charset/group
> decoding stuff, stop encoding/decoding altogether, but I don't know how
> I would prove that wouldn't cause problems.
>
> Can you just not use gnus-group-decoded-name? As I mentioned, decoding
> as 'utf-8-emacs should work fine.
>
> Eric
Yes, I agree with you and will take your advice.
Thanks for discussing the issue.
For my needs, I will just replace gnus-group-name-decode with:
#+begin_src emacs-lisp
(defun gnus-recent-decode-utf8 (string &optional charset)
"Decode a gnus-group name.
Replaces `gnus-group-name-decode' for decoding group names.
Default utf-8-emacs CHARSET unless provided otherwise."
(decode-coding-string string (or charset 'utf-8-emacs) t))
#+end_src
I guess you may close the bug.
next prev parent reply other threads:[~2020-01-13 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 2:47 bug#39026: 27.0.50; gnus-group-decoded-name needs running gnus Deus Max
2020-01-08 19:09 ` Eric Abrahamsen
2020-01-09 13:22 ` Deus Max
2020-01-13 18:51 ` Eric Abrahamsen
2020-01-13 20:57 ` Deus Max [this message]
2020-01-14 22:54 ` Eric Abrahamsen
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=874kwz6pnh.fsf@aia00054aia.gr \
--to=deusmax@gmx.com \
--cc=39026@debbugs.gnu.org \
--cc=eric@ericabrahamsen.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/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).