progfolio
commented
1 year ago git version 2.38.1
That's pretty close to what I have, so I doubt the error is due to the git version. There's probably an error in the constructed git clone command.
I typed in #verbosity after pressing s but the result looks the same. Is verbosity a search tag? I didn't see it in elpaca-ui-search-tags.
It is a search tag, but it is implemented in elpaca-log.el. The log buffer should have elpaca-ui-search-tags set buffer-locally to include elpaca-log-search-tags (which holds tags that only make sense in the context of a log buffer). You can check by evaluating M-x describe-variable elpaca-ui-search-tags from within the log buffer. The commands are shown in the output correctly.
From your log:
elpaca cloning $git clone Elpaca Log (41 matches) #unique !finished https://github.com/progfolio/elpaca.git /home/luis/.config/emacs/elpaca/repos/elpaca.github.progfolio/ 95.332654
Is this actually the text in the log or did you accidentally paste "Elpaca Log (41 matches) #unique !finished" into the log output?
Luis-Henriquez-Perez
Feature Description
Either a certain parameter of a function or macro, or a variable (probably the former would be preferable) that forces
elpacato install packages synchronously.when asynchronous installation is desirable
I understand that
elpacais specifically designed to work asynchronously so a synchronous install would be an "anti-feature".Sometimes in which an asynchronous install of packages is preferable. For me this is nice when installing a package during an active emacs session. You can use
elpaca-tryto install one or more packages, and do other things while waiting for them to be installed.recommended solution: put your init in
elpaca-after-init-hookThe solution suggested for why did my init file execute out of order is to move all of your init file (or at least the external package dependant parts of it) into
elpaca-after-init-hook. This way this code will be run only after package installation as ended.practical problem to asynchronous installation : missing timing
Even if you follow the recommended solution, you still miss potentially the entire startup process when installing a sufficiently large number of packages. So any code you have involving
after-init-hook,before-init-hook,frame-notice-user-settings, .etc has to be revised and likely modified so that it still works even if it missed timing.stylistic and idealogical problems with suggested solution
In my opinion, requiring to move all their init file contents into a hook to accommodate a single emacs package is unreasonable. A package should require installation, configuration and installation of any dependencies it needs, but it shouldn't entail a restructuring of your entire config solely to meet its own needs.
installing packages asynchronously at startup does not benefit many users
I suspect many Emacs users like me have a config file that heavily relies on external packages--so much so that not having those packages would make emacs unusable for them. For these users, an asynchronous package installation during startup does not benefit them as much because even if emacs is unblocked, it would be too inconvenient to use until their main packages are installed.
others who have mentioned this
I am not the only one who has been concerned about this. I assert that enough users have expressed interest in a synchronous installation for it to be added as an alternative.
https://github.com/progfolio/elpaca/issues/29#issuecomment-1323506198 https://github.com/progfolio/elpaca/issues/29#issuecomment-1345689506 https://github.com/progfolio/elpaca/issues/7#issuecomment-1300662283 https://github.com/progfolio/elpaca/issues/7#issuecomment-1253367568
Confirmation