Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

Doom Emacs step fails with 'Error: unknown option -y' #960

Open
mayersj1 opened this issue Jun 21, 2022 · 2 comments · May be fixed by #968
Open

Doom Emacs step fails with 'Error: unknown option -y' #960

mayersj1 opened this issue Jun 21, 2022 · 2 comments · May be fixed by #968

Comments

@mayersj1
Copy link

What did you expect to happen?

Doom emacs upgrade script would run

What actually happened?

Doom emacs step failed with the following error info:

―― 10:28:46 - Doom Emacs ―――――――――――――――――――――――――――――――――――――――――――――――――――――――
Error: unknown option -y

Usage: doom [-!|--force] [-D|--debug] [--doomdir DIR] [--emacsdir DIR]
[--pager BOOL] [--[no-]color] [-L|--load|--strict-load
FILE]... [-E|--eval FORM]... [--] COMMAND [ARGS...]

See 'doom h[elp]' or 'doom {-?,--help}' for documentation.

Additional details

  • Which operating system or Linux distribution are you using?
  • How did you install Topgrade?

MacOS 12.4 Monterey
Topgrade installed via Homebrew

Paste the output of `topgrade -v`
@xeruf
Copy link
Contributor

xeruf commented Jul 1, 2022

The step seems completely broken now:

❯ topgrade --only emacs
❯ doom upgrade
> Preparing to upgrade Doom Emacs and its packages...
- A new version of Doom Emacs is available!

it just exits with exit code 0 doing nothing, even though there is clearly an update available

@reinaldoossuna reinaldoossuna linked a pull request Jul 6, 2022 that will close this issue
@reinaldoossuna
Copy link

@xeruf try to run that topgrade --only emacs -v. it's should be something like that:

topgrade --only emacs -v
....
Emacs: SKIPPED: Path "/home/nardo/.emacs.d/init.el" doesn't exist

the hack solution it's to create a init.el.

touch ~/.emacs.d/init.el

Now it's should be fail because there is no option -y flag anymore, #968 fixes that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants