You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
opam pin add --edit pauses before launching the editor even when given --yes and setting OPAMEDITOR.
I would have expected --yes (and --no) to make opam switch to non-interactive mode (maybe it would make more sense to have a dedicated option to set the non-interactive mode, namely picking the default choice, not always yes or no).
Getting a “Press enter to start ...” message before opening an editor in an --edit command made me look again at what git does before opening an editor: it just displays “hint: Waiting for your editor to close the file...” in case something goes wrong there but doesn’t pause (and clears the message as soon as the editor finishes). But maybe we can safely assume git users have an editor configured, opam users less so.
I did get the behaviour I was looking for by running opam pin ... < /dev/null as, in my case, the chosen OPAMEDITOR is not interactive.
(I’m running version 2.1.6 but I think that part of the code didn’t change in master.)
The text was updated successfully, but these errors were encountered:
opam pin add --edit
pauses before launching the editor even when given--yes
and settingOPAMEDITOR
.I would have expected
--yes
(and--no
) to makeopam
switch to non-interactive mode (maybe it would make more sense to have a dedicated option to set the non-interactive mode, namely picking the default choice, not always yes or no).Getting a “Press enter to start ...” message before opening an editor in an
--edit
command made me look again at whatgit
does before opening an editor: it just displays “hint: Waiting for your editor to close the file...” in case something goes wrong there but doesn’t pause (and clears the message as soon as the editor finishes). But maybe we can safely assume git users have an editor configured, opam users less so.I did get the behaviour I was looking for by running
opam pin ... < /dev/null
as, in my case, the chosenOPAMEDITOR
is not interactive.(I’m running version 2.1.6 but I think that part of the code didn’t change in
master
.)The text was updated successfully, but these errors were encountered: