From: Adriano Peluso <randomlooser@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-user@gnu.org
Subject: Re: guile studio
Date: Fri, 04 Jun 2021 13:50:29 +0200 [thread overview]
Message-ID: <228b9c7e08b43c95ae67406cc8e7e6c048487cc6.camel@riseup.net> (raw)
In-Reply-To: <874kegwnvp.fsf@elephly.net>
Il giorno mer, 02/06/2021 alle 12.40 +0200, Ricardo Wurmus ha scritto:
>
> Adriano Peluso <randomlooser@riseup.net> writes:
>
> > Il giorno lun, 31/05/2021 alle 11.45 +0200, Ricardo Wurmus ha
> > scritto:
> >
> >
> >
> > > Hmm, this is a little confusing. Perhaps something is missing
> > > in
> > > Guile Studio to prevent accidental loading of existing Emacs
> > > packages. The wrapper overrides EMACSLOADPATH and then
> > > launches a
> > > particular version of Emacs without the site file, and then
> > > loads
> > > all the packages from EMACSLOADPATH. I wonder if it
> > > accidentally
> > > picks up *other* packages as well.
> > >
> >
> > Can I help in any way ?
>
> Can you confirm that the presence of ~/.emacs.d prevents
> guile-studio from starting correctly? I would then try to
> reproduce this and figure out how to prevent this problem.
>
Well, I can't confirm
In fact, I reinstated my old .emacs.d folder, the one containing the
configuration based on Straight, and now guile-studio starts up
correctly, it seems
I can't explain this, it didn't start up properly, I swear 🤷️
next prev parent reply other threads:[~2021-06-04 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 11:53 guile studio Adriano Peluso
2021-05-27 11:57 ` Adriano Peluso
2021-05-29 19:45 ` Ricardo Wurmus
2021-05-29 20:23 ` Ricardo Wurmus
2021-05-30 6:04 ` Adriano Peluso
2021-05-30 16:56 ` Adriano Peluso
2021-05-31 9:45 ` Ricardo Wurmus
2021-06-02 9:10 ` Adriano Peluso
2021-06-02 10:40 ` Ricardo Wurmus
2021-06-04 11:50 ` Adriano Peluso [this message]
2021-06-04 11:55 ` Ricardo Wurmus
[not found] <mailman.533.1624102324.10239.guile-user@gnu.org>
2021-06-19 12:13 ` Kjetil Matheussen
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=228b9c7e08b43c95ae67406cc8e7e6c048487cc6.camel@riseup.net \
--to=randomlooser@riseup.net \
--cc=guile-user@gnu.org \
--cc=rekado@elephly.net \
/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).