unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Akib Azmain Turja <akib@disroot.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Compiling Emacs from source for hacking on it
Date: Wed, 01 Jun 2022 00:11:55 +0600	[thread overview]
Message-ID: <87czftshas.fsf@disroot.org> (raw)
In-Reply-To: <834k15irla.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Akib Azmain Turja <akib@disroot.org>
>> Cc: emacs-devel@gnu.org
>> Date: Tue, 31 May 2022 22:22:31 +0600
>> 
>> > If using "-Q" doesn't help, perhaps this is some problem with building
>> > in a separate directory, in which case you could rebuild in-place and
>> > try again.
>> 
>> Yes, adding -Q works.  But why it can't read my init file even when the
>> whole file is commented?  Or is it expected?
>
> If using -Q solves the problem, look for the reason in your init files
> or site-init files.  Also, maybe you have some installed packages that
> get activated at startup?

Ahh, I didn't thought about that.  Guix and package is loading autoloads
which might cause it.  But interestingly, the "with-memoization is
undefined" problem doesn't occur when I call temacs.

>
> However, if all you need is to make changes in Emacs, maybe you can
> always invoke this version-for-hacking with -Q?

Yeah, I would probably do so, but I was just testing if everything was
working correctly.

-- 
Akib Azmain Turja

This message is signed by me with my GnuPG key.  It's fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2022-05-31 18:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 12:07 Compiling Emacs from source for hacking on it Akib Azmain Turja
2022-05-31 12:45 ` Po Lu
2022-05-31 13:35   ` tomas
2022-05-31 13:42     ` Ken Brown
2022-05-31 14:01       ` tomas
2022-05-31 14:02       ` Óscar Fuentes
2022-05-31 14:10         ` tomas
2022-05-31 14:18           ` Óscar Fuentes
2022-05-31 16:27   ` Akib Azmain Turja
2022-05-31 16:55     ` Lars Ingebrigtsen
2022-05-31 18:16       ` Akib Azmain Turja
2022-05-31 18:18         ` Lars Ingebrigtsen
2022-05-31 13:06 ` Eli Zaretskii
2022-05-31 13:43   ` Eli Zaretskii
2022-05-31 16:22   ` Akib Azmain Turja
2022-05-31 16:39     ` Eli Zaretskii
2022-05-31 18:11       ` Akib Azmain Turja [this message]
2022-05-31 18:30         ` Akib Azmain Turja
2022-05-31 19:22           ` Eli Zaretskii
2022-06-01  1:10             ` Akib Azmain Turja
2022-06-01  2:42               ` Eli Zaretskii
2022-06-01 11:26                 ` Akib Azmain Turja
2022-06-01 12:15                   ` Eli Zaretskii
2022-06-01 12:41                     ` Akib Azmain Turja
2022-06-01 13:03                       ` Akib Azmain Turja
2022-06-01 13:13                         ` Eli Zaretskii
2022-06-01 13:07                       ` Eli Zaretskii
2022-06-01 16:36                         ` Akib Azmain Turja
2022-06-01 17:23                           ` Eli Zaretskii
2022-06-02 10:52         ` Philip Kaludercic
2022-06-02 16:47           ` Akib Azmain Turja
2022-05-31 14:17 ` Andreas Schwab
2022-05-31 14:23   ` Visuwesh
2022-05-31 16:24     ` Akib Azmain Turja
2022-05-31 14:52   ` Michael Heerdegen
2022-05-31 16:24     ` Akib Azmain Turja
2022-05-31 16:25   ` Akib Azmain Turja

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=87czftshas.fsf@disroot.org \
    --to=akib@disroot.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).