From: "T.V Raman" via "Emacs development discussions." <emacs-devel@gnu.org>
To: arthur.miller@live.com
Cc: contovob@tcd.ie, emacs-devel@gnu.org, raman@google.com
Subject: Re: package-quickstart: How To Debug?
Date: Mon, 21 Dec 2020 09:30:06 -0800 [thread overview]
Message-ID: <24544.56222.62606.857165@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <AM0PR06MB6577887EC0F1634E3E65338396C00@AM0PR06MB6577.eurprd06.prod.outlook.com>
The failure likely started after I built from master:-) I usually
build emacs once a day -- and it may well have gone away now --Arthur Miller writes:
> "T.V Raman" <raman@google.com> writes:
>
> > Interesting. From what I remember, package-quickstart was bombing out
> > because of calls to eieio -- likely due to some macro expansion
> > error. I've worked around it for now by uninstalling marhsall and what
> > needed it --- given that Emacs is my primary/only environment for
> > geting spoken feedback without which I cannot work productively, I'm
> > not going to go chase this further --- Emacs not starting makes
> > things very hard :-)
> Yes, I understand you. It is pain when Emacs does not start at all, I
> hate it myself.
>
> If Emacs does not start because of quickstart, you can always run it
> with -Q or -q flags, so quickstart wont come into play.
>
> But as said; I installed those and byte-compiled quickstart file and it
> worked. So it can be something else in your setup. Or maybe just older
> Emacs bombs out? Have you tried to build newer from the master?
--
♉Id: kg:/m/0285kf1 🦮♉
--
♉Id: kg:/m/0285kf1 🦮♉
next prev parent reply other threads:[~2020-12-21 17:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 18:10 package-quickstart: How To Debug? T.V Raman
2020-12-20 18:21 ` Basil L. Contovounesios
2020-12-20 18:55 ` T.V Raman
2020-12-20 21:31 ` Stefan Monnier
2020-12-20 21:47 ` arthur miller
2020-12-21 1:43 ` T.V Raman
2020-12-21 2:23 ` arthur miller
2020-12-21 16:53 ` Arthur Miller
2020-12-21 17:12 ` T.V Raman via Emacs development discussions.
2020-12-21 17:18 ` Arthur Miller
2020-12-21 17:30 ` T.V Raman via Emacs development discussions. [this message]
2020-12-21 18:21 ` Stefan Monnier
2020-12-21 18:31 ` T.V Raman via Emacs development discussions.
2020-12-21 18:43 ` T.V Raman via Emacs development discussions.
2020-12-21 19:12 ` Stefan Monnier
2020-12-21 19:18 ` T.V Raman via Emacs development discussions.
2020-12-21 17:56 ` Stefan Monnier
2020-12-21 18:12 ` T.V Raman via Emacs development discussions.
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=24544.56222.62606.857165@retriever.mtv.corp.google.com \
--to=emacs-devel@gnu.org \
--cc=arthur.miller@live.com \
--cc=contovob@tcd.ie \
--cc=raman@google.com \
/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).