all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 34707@debbugs.gnu.org
Subject: bug#34707: Failure to find the associated pdump file
Date: Mon, 04 Mar 2019 05:36:58 +0200	[thread overview]
Message-ID: <83y35ve2ed.fsf@gnu.org> (raw)
In-Reply-To: <E1h0eFk-0006rb-Jg@fencepost.gnu.org> (message from Richard Stallman on Sun, 03 Mar 2019 22:26:56 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: 34707@debbugs.gnu.org
> Date: Sun, 03 Mar 2019 22:26:56 -0500
> 
>   > If the file is not found, Emacs behaves like temacs: it loads the Lisp
>   > files before proceeding.  It sounds like in your case it didn't do tat
>   > because it found no Lisp files, is that right?
> 
> It did find the Lisp directory -- that code is old and knows how to
> follow the symlink.  But that's not the issue, because
> "tty-set-up-initial-frame-faces" is supposed to be preloaded.
> 
> I think you said this problem is fixed now.

Yes, it was an unrelated bug, which went unnoticed because no one
tried "emacs -nw" in the situation where the pdump file cannot be
found.





  reply	other threads:[~2019-03-04  3:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02  3:27 bug#34707: Failure to find the associated pdump file Richard Stallman
2019-03-02  7:11 ` Eli Zaretskii
2019-03-03  2:58   ` Richard Stallman
2019-03-03  3:45     ` Eli Zaretskii
2019-03-04  3:28       ` Richard Stallman
2019-03-03  2:58   ` Richard Stallman
2019-03-03  3:41     ` Eli Zaretskii
2019-03-03 17:08       ` Eli Zaretskii
2019-03-04  3:26       ` Richard Stallman
2019-03-04  3:36         ` Eli Zaretskii [this message]
2019-03-03 17:06     ` Eli Zaretskii
2019-06-17 18:56 ` Lars Ingebrigtsen
2019-06-17 19:23   ` Eli Zaretskii
2019-06-18  3:07   ` Richard Stallman
2019-06-28  6:42     ` Eli Zaretskii

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=83y35ve2ed.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34707@debbugs.gnu.org \
    --cc=rms@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 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.