unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: ken <gebser@mousecar.com>
To: help-gnu-emacs@gnu.org
Subject: Re: finding the hork point in ~/.emacs: timerp
Date: Fri, 28 Aug 2020 08:26:22 -0400	[thread overview]
Message-ID: <4819eb23-4ddd-ff44-0be1-d3d24de1a739@mousecar.com> (raw)
In-Reply-To: <83mu2fyq7p.fsf@gnu.org>

On 8/28/20 7:17 AM, Eli Zaretskii wrote:
>> From: ken <gebser@mousecar.com>
>> Date: Fri, 28 Aug 2020 06:50:34 -0400
>> Cc: help-gnu-emacs@gnu.org
>>
>>> You could try
>>>
>>> (setq debug-on-message "Error during redisplay")
>>>
>>> at the top of your .emacs. Although I suspect grepping through your
>>> package code might be quicker (thatʼs typically somewhere under
>>> "~/.emacs.d")
>>>
>>> Roert
>> Good suggestion about the text search, but "grep -ri timerp *" returned
>> nothing.
> As I said in another message, you should drop everything and first
> resolve the problem with Emacs not finding its emacs.pdmp file.  That
> long series of "Loading foo..." messages should never appear at
> startup time.
>
> How did you install Emacs? are there any symlinks or other redirection
> methods involved in reaching the Emacs executable from its usual
> place?
>
In another post in this thread I talked about emacs.pdmp in a bit more
detail... essentially I don't have that file on my system, nor was it
part of the install.

This system is fairly new, installed just a week or so ago:

# ll /etc/os-release
lrwxrwxrwx 1 root root 21 Aug 17 17:22 /etc/os-release ->
../usr/lib/os-release
# cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20200817"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20200817"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20200817"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
LOGO="distributor-logo"

# whereis -b emacs
emacs: /usr/bin/emacs /usr/lib/emacs /usr/share/emacs
# ls -ld /usr/bin/emacs /usr/lib/emacs /usr/share/emacs
-rwxr-xr-x 1 root root 4334 Apr 26  2017 /usr/bin/emacs
drwxr-xr-x 1 root root    8 Aug 18 16:26 /usr/lib/emacs
drwxr-xr-x 1 root root   42 Aug 18 16:26 /usr/share/emacs






  reply	other threads:[~2020-08-28 12:26 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 20:08 finding the hork point in ~/.emacs ken
2020-08-26 20:10 ` Yuan Fu
2020-08-26 20:12 ` Stefan Kangas
2020-08-26 22:38   ` ken
2020-08-26 23:27     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-26 23:39       ` ken
2020-08-27  0:23         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-27  4:08     ` Eli Zaretskii
2020-08-27 17:24       ` ken
2020-08-27 17:42         ` Eli Zaretskii
2020-08-27 22:40           ` ken
2020-08-28  6:41             ` Eli Zaretskii
2020-08-28 11:56               ` ken
2020-08-27 17:17     ` finding the hork point in ~/.emacs: timerp ken
2020-08-27 17:34       ` Noam Postavsky
2020-08-28 10:07         ` hork point in ~/.emacs: -Q and --debug outputs in terminal & *Messages* ken
2020-08-28 11:13           ` Eli Zaretskii
2020-08-28 12:08             ` ken
2020-08-28 12:39               ` Eli Zaretskii
2020-08-28 13:02                 ` ken
2020-08-28 13:19                   ` Eli Zaretskii
     [not found]                     ` <d4982eda-fd8a-c2fd-3342-b446d83218fc@mousecar.com>
2020-08-29 12:47                       ` Eli Zaretskii
2020-08-29 16:02                         ` hork point in ~/.emacs: needing emacs.pdmp & other ken
2020-08-29 18:13                           ` Eli Zaretskii
2020-08-29 18:59                             ` Yuri Khan
2020-08-29 19:21                               ` Eli Zaretskii
2020-08-29 21:49                             ` Togan Muftuoglu via Users list for the GNU Emacs text editor
2020-08-31 11:30                             ` ken
2020-08-28 13:13                 ` hork point in ~/.emacs: -Q and --debug outputs in terminal & *Messages* ken
2020-08-28 13:21                   ` Eli Zaretskii
2020-08-27 17:41       ` finding the hork point in ~/.emacs: timerp Robert Pluim
2020-08-27 17:43         ` Noam Postavsky
2020-08-28 10:50         ` ken
2020-08-28 11:17           ` Eli Zaretskii
2020-08-28 12:26             ` ken [this message]
2020-08-28 12:41               ` Eli Zaretskii
2020-08-29 12:14                 ` ken
2020-08-28 12:46             ` finding the hork point in ~/.emacs -> emacs.pdmp ken
2020-08-26 20:52 ` finding the hork point in ~/.emacs Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-26 23:37   ` ken
2020-08-27  0:46     ` Eric Abrahamsen
2020-08-27  2:18       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-27  0:53 ` Carson Chittom
2020-08-27  1:42   ` Drew Adams
2020-08-27  2:27     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-27  2:58       ` Drew Adams
2020-08-27  4:23         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-27  4:57           ` Drew Adams
2020-08-27  5:06             ` Emanuel Berg via Users list for the GNU Emacs text editor
     [not found]   ` <mailman.1413.1598489645.2469.help-gnu-emacs@gnu.org>
2020-08-27  1:53     ` Ihor Radchenko
2020-08-27  2:19   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-27  2:59     ` Drew Adams

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=4819eb23-4ddd-ff44-0be1-d3d24de1a739@mousecar.com \
    --to=gebser@mousecar.com \
    --cc=help-gnu-emacs@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.
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).