From: Kenichi Handa <handa@m17n.org>
Cc: handa@m17n.org
Subject: Re: non-ASCII TAGS
Date: Wed, 23 Apr 2003 20:01:04 +0900 (JST) [thread overview]
Message-ID: <200304231101.UAA04310@etlken.m17n.org> (raw)
In-Reply-To: <rzqu1dgiz0i.fsf@albion.dl.ac.uk> (message from Dave Love on 02 Apr 2003 18:34:53 +0100)
Sorry for the late response on this matter.
In article <rzqu1dgiz0i.fsf@albion.dl.ac.uk>, Dave Love <d.love@dl.ac.uk> writes:
> Probably the worst problem with using non-ASCII programming
> identifiers is etags. It isn't aware of encoding issues and fixing
> the issues is non-trivial, so this is mainly raising a flag and hoping
> someone can work on it. I think sorting it out requires not only
> extending the TAGS format, but probably also generating it with Emacs.
> I don't have time to work on this, but here's the problem and some
> ideas.
What do you think about the following proposal which, I
think, work in most cases without extending the TAGS format.
In the case it doesn't work, we can still ask people to use
C-x RET c __CODING__ RET ESC . .
Of course, as you wrote, recoding coding systems in TAGS is
ideal, but it requires more work just to save rare cases.
Kenichi Handa <handa@m17n.org> writes:
> In article <shpto57wa4.fsf_-_@tux.gnu.franken.de>, Karl Eichwalder <keichwa@gmx.net> writes:
>> Now the next one: `tags-query-replace' does not work properly when file
>> names are UTF-8 encoded. First run `etags *' on the files and then
>> call `tags-query-replace'.
> This is the same type of bug (but more difficult) as what I
> posted to emacs-devel by the subjest "bad interaction with
> C-x RET c and vc-cvs-registered".
> A tag file contains file names plus parts of source code.
> The former must be decoded by file-name-coding-system, but
> the latter must be decoded by the coding system of each
> file. It's very hard to decided a coding system for the
> latter without actually reading the file.
> Perhaps, a tag file must be read as raw-text (thus in a
> unibyte buffer), and if one gives a non-ASCII TAGNAME to
> `find-tag', it must be encoded by the
> buffer-file-coding-system of the current buffer.
And the reply from Richard is as follows:
> That seems like a good approach. Would someone like to implement it?
---
Ken'ichi HANDA
handa@m17n.org
prev parent reply other threads:[~2003-04-23 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 17:34 non-ASCII TAGS Dave Love
2003-04-23 11:01 ` Kenichi Handa [this message]
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=200304231101.UAA04310@etlken.m17n.org \
--to=handa@m17n.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).