From: Dan Nicolaescu <dann@ics.uci.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: 909@emacsbugs.donarmstrong.com
Subject: bug#909: not finding etc/charsets/ should give some error/warning
Date: Wed, 10 Sep 2008 23:37:23 -0700 [thread overview]
Message-ID: <200809110637.m8B6bNm1023329@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <fad4jbu374.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 10 Sep 2008 16:59:59 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Dan Nicolaescu wrote:
>
> > It would be great if some warning/error would be shown if
> > etc/charsets/* is not found.
>
> *** charset.c 3 Jun 2008 04:22:55 -0000 1.163
> --- charset.c 10 Sep 2008 21:00:06 -0000
> ***************
> *** 2044,2052 ****
> void
> init_charset ()
> {
> ! Vcharset_map_path
> ! = Fcons (Fexpand_file_name (build_string ("charsets"), Vdata_directory),
> ! Qnil);
> }
>
>
> --- 2044,2055 ----
> void
> init_charset ()
> {
> ! Lisp_Object tempdir;
> ! tempdir = Fexpand_file_name (build_string ("charsets"), Vdata_directory);
> ! if (access (SDATA (tempdir), 0) < 0)
> ! dir_warning ("Warning: charsets directory (%s) does not exist.\n",
> ! tempdir);
Thanks.
How about saying something like "Emacs will not function correctly in
this condition", or something of the sort, to emphasize that the
situation is quite bad?
next prev parent reply other threads:[~2008-09-11 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <34iqt2jby4.fsf@fencepost.gnu.org>
2008-09-07 11:19 ` bug#909: not finding etc/charsets/ should give some error/warning Dan Nicolaescu
2008-09-10 20:59 ` Glenn Morris
2008-09-11 6:37 ` Dan Nicolaescu [this message]
2008-09-11 7:11 ` Glenn Morris
2008-09-11 8:37 ` Andreas Schwab
2008-09-11 16:09 ` Glenn Morris
2008-09-12 3:20 ` bug#909: marked as done (not finding etc/charsets/ should give some error/warning) Emacs bug Tracking System
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=200809110637.m8B6bNm1023329@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=909@emacsbugs.donarmstrong.com \
--cc=rgm@gnu.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).