-
-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is $SECURITYSESSIONID needed to check? #72
Comments
I borrowed this check from Git, which has since changed the conditional: git/git@be537e4. Does adding a check for |
Ah, I got the reason for the code clearly by the comment in git's commit. |
delphinus
added a commit
to delphinus/vim-eunuch
that referenced
this issue
Aug 5, 2020
Use the way how git does. See below. git/git@be537e4
tpope
pushed a commit
that referenced
this issue
Aug 7, 2020
Use the way how git does. See below. git/git@be537e4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using NeoVim and know
:SudoWrite
cannot work by default settings. So I searched issues and found a workaround in #56 (comment) .I tried this workaround but still it did not work. So I invested the source and found here.
vim-eunuch/plugin/eunuch.vim
Line 189 in 36c5974
@tpope says this line detects the env is NeoVim in local ( #45 (comment) ). But is
$SECURITYSESSIONID
needed to check? At least in my env (macOS Mojave 10.14.6),$SECURITYSESSIONID
is always empty even in local.For a stopgap measure, I wrote below in
init.vim
and successfully:SudoWrite
works! thx @TSFoster !The text was updated successfully, but these errors were encountered: