unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: Help debugging a backtrace
Date: Mon, 02 May 2016 15:10:17 +0000	[thread overview]
Message-ID: <CAFyQvY0DsOAZmYKAfWZf-u77NxV8U0A1D5rUHEWqVkvcXtar5A@mail.gmail.com> (raw)
In-Reply-To: <87wpnc7cfh.fsf@web.de>

Hi Michael,

Thanks for your time and continuous support.

Unless someone finds time to debug the problem in this thread, as I see
this issue only on my phone build, the workaround I am using is to not put
(package-initialize) in a separate file, but in init.el itself.

It's unfortunate though that the problem is related to the location of
(package-initialize) in my emacs config.

On Mon, May 2, 2016 at 10:39 AM Michael Heerdegen <michael_heerdegen@web.de>
wrote:

> Kaushal Modi <kaushal.modi@gmail.com> writes:
>
> > I also confirmed that when I do not do (package-initialize) from
> > outside init.el, attempt to require finder-inf.el is not made from
> > within loadup.el. In that case, the only load-file-name is the
> > init.el.
>
> Hmm, I read everything carefully.  I didn't find anything obviously
> bogus or wrong, including the termux hacks.
>
> Maybe you have just hit, by accident, a bug that is also present in
> vanilla Emacs, and it's nothing wrong with your stuff.  If there is
> something wrong with it, I have no clue what it could be.
>
>
> Michael.
>
>
> --

-- 
Kaushal Modi


  reply	other threads:[~2016-05-02 15:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 18:28 Help debugging a backtrace Kaushal Modi
2016-04-27 19:01 ` Nick Dokos
2016-04-27 19:37   ` Kaushal Modi
2016-04-28 20:59     ` Kaushal Modi
2016-04-29 21:27       ` Michael Heerdegen
2016-04-29 21:36         ` Kaushal Modi
2016-04-29 22:56           ` Kaushal Modi
2016-05-01 14:22             ` Michael Heerdegen
2016-05-01 14:27               ` Michael Heerdegen
2016-05-01 19:05                 ` Kaushal Modi
2016-05-01 20:45                   ` Michael Heerdegen
2016-05-01 21:10                     ` Drew Adams
2016-05-02  4:20                       ` Kaushal Modi
2016-05-02  4:38                         ` Kaushal Modi
2016-05-02 14:38                           ` Michael Heerdegen
2016-05-02 15:10                             ` Kaushal Modi [this message]
2016-05-02 15:33                               ` Eli Zaretskii
     [not found] <mailman.1147.1461781734.7477.help-gnu-emacs@gnu.org>
2016-09-06  7:26 ` rn3aoh.g
2016-09-20 16:15   ` Kaushal Modi
2016-09-21  1:53     ` Jude DaShiell
2016-09-21 17:12       ` Kaushal Modi
2016-09-22 18:52         ` Jude DaShiell

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=CAFyQvY0DsOAZmYKAfWZf-u77NxV8U0A1D5rUHEWqVkvcXtar5A@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).