From: Eli Zaretskii <eliz@gnu.org>
To: ohki@gssm.otsuka.tsukuba.ac.jp,
Daniel Colascione <dancol@dancol.org>,
John Wiegley <johnw@gnu.org>
Cc: 22815@debbugs.gnu.org
Subject: bug#22815: 25.0.91; emacs-module.*
Date: Sat, 27 Feb 2016 10:19:50 +0200 [thread overview]
Message-ID: <83h9gud0pl.fsf@gnu.org> (raw)
In-Reply-To: <4539.1456528899@smr00> (ohki@gssm.otsuka.tsukuba.ac.jp)
> From: ohki@gssm.otsuka.tsukuba.ac.jp
> Cc: ohki@gssm.otsuka.tsukuba.ac.jp, 22815@debbugs.gnu.org
> Date: Sat, 27 Feb 2016 08:21:39 +0900
>
> Eli Zaretskii writes:
> > > From: ohki@gssm.otsuka.tsukuba.ac.jp
> > > Cc: ohki@gssm.otsuka.tsukuba.ac.jp, 22815@debbugs.gnu.org
> > > Date: Fri, 26 Feb 2016 19:09:57 +0900
> > >
> > > > I was asking why couldn't the plug-in do the conversion, e.g., by
> > > > using libiconv? Emacs is not the only piece of software that knows
> > > > how to convert from one encoding to another.
> > >
> > > I considered using libiconv once, but Emacs has the conversion
> > > capability, so why not use it.
> >
> > Because it can signal an error, if the encoding you pass is not a
> > valid coding-system that Emacs recognizes?
>
> Yes it does!
> In the course of developing my plugin,
> I encountered `Invalid coding system' message, and Emacs keep working
> (no crash, no hangup).
It's all too easy to get that, since Emacs coding-systems have names
that are rarely used elsewhere. And using libiconv is easy enough.
So I'm uneasy about this. What do others think?
next prev parent reply other threads:[~2016-02-27 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 7:28 bug#22815: 25.0.91; emacs-module.* Atsuo Ohki
2016-02-26 9:10 ` Eli Zaretskii
2016-02-26 9:16 ` ohki
2016-02-26 9:46 ` Eli Zaretskii
2016-02-26 10:09 ` ohki
2016-02-26 18:26 ` Eli Zaretskii
2016-02-26 23:21 ` ohki
2016-02-27 8:19 ` Eli Zaretskii [this message]
2016-03-29 10:05 ` Philipp Stephani
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h9gud0pl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22815@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=johnw@gnu.org \
--cc=ohki@gssm.otsuka.tsukuba.ac.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.