Can't make vimwiki honor setting passed via command line
I am trying to write a wrapper shell script that is supposed to launch vim with a vimwiki in current directory:
#!/bin/bash
gvim -c "let g:vimwiki_list = [{'path': '$PWD/'}] | normal ,ww"
The normal command works (the comma is my custom remapped <Leader>), but it doesn't honor the custom path option.
To reproduce the problem, just run the above script somewhere not in home directory. At startup, vim will ask to create ~/vimwiki instead of using current working directory. Yet after I skip that question and do
:echo g:vimwiki_list
in vim's command line, it displays the correct current directory. So it's not a problem of the correct value of $PWD getting passed to vim, I use the bash variable inside double quotes so this part is fine.
How to debug and eventually fix it?
I had a customized g:vimwiki_list in my vimrc, but I also tried with defaults by commenting that part, the problem still persists (Is it true that settings passed via command line the way I did aren't overwritten by the ones hardcoded in vimrc anyway?).
linux plugin-vimwiki
asked Feb 21 at 10:02
AnonymousLurkerAnonymousLurker
2007
add a comment |
I am trying to write a wrapper shell script that is supposed to launch vim with a vimwiki in current directory:
#!/bin/bash
gvim -c "let g:vimwiki_list = [{'path': '$PWD/'}] | normal ,ww"
The normal command works (the comma is my custom remapped <Leader>), but it doesn't honor the custom path option.
To reproduce the problem, just run the above script somewhere not in home directory. At startup, vim will ask to create ~/vimwiki instead of using current working directory. Yet after I skip that question and do
:echo g:vimwiki_list
in vim's command line, it displays the correct current directory. So it's not a problem of the correct value of $PWD getting passed to vim, I use the bash variable inside double quotes so this part is fine.
How to debug and eventually fix it?
I had a customized g:vimwiki_list in my vimrc, but I also tried with defaults by commenting that part, the problem still persists (Is it true that settings passed via command line the way I did aren't overwritten by the ones hardcoded in vimrc anyway?).
linux plugin-vimwiki
asked Feb 21 at 10:02
AnonymousLurkerAnonymousLurker
2007
add a comment |
I am trying to write a wrapper shell script that is supposed to launch vim with a vimwiki in current directory:
#!/bin/bash
gvim -c "let g:vimwiki_list = [{'path': '$PWD/'}] | normal ,ww"
The normal command works (the comma is my custom remapped <Leader>), but it doesn't honor the custom path option.
To reproduce the problem, just run the above script somewhere not in home directory. At startup, vim will ask to create ~/vimwiki instead of using current working directory. Yet after I skip that question and do
:echo g:vimwiki_list
in vim's command line, it displays the correct current directory. So it's not a problem of the correct value of $PWD getting passed to vim, I use the bash variable inside double quotes so this part is fine.
How to debug and eventually fix it?
I had a customized g:vimwiki_list in my vimrc, but I also tried with defaults by commenting that part, the problem still persists (Is it true that settings passed via command line the way I did aren't overwritten by the ones hardcoded in vimrc anyway?).
linux plugin-vimwiki
asked Feb 21 at 10:02
AnonymousLurkerAnonymousLurker
2007
I am trying to write a wrapper shell script that is supposed to launch vim with a vimwiki in current directory:
#!/bin/bash
gvim -c "let g:vimwiki_list = [{'path': '$PWD/'}] | normal ,ww"
The normal command works (the comma is my custom remapped <Leader>), but it doesn't honor the custom path option.
To reproduce the problem, just run the above script somewhere not in home directory. At startup, vim will ask to create ~/vimwiki instead of using current working directory. Yet after I skip that question and do
:echo g:vimwiki_list
in vim's command line, it displays the correct current directory. So it's not a problem of the correct value of $PWD getting passed to vim, I use the bash variable inside double quotes so this part is fine.
How to debug and eventually fix it?
I had a customized g:vimwiki_list in my vimrc, but I also tried with defaults by commenting that part, the problem still persists (Is it true that settings passed via command line the way I did aren't overwritten by the ones hardcoded in vimrc anyway?).
linux plugin-vimwiki
linux plugin-vimwiki
asked Feb 21 at 10:02
AnonymousLurkerAnonymousLurker
2007
asked Feb 21 at 10:02
AnonymousLurkerAnonymousLurker
2007
asked Feb 21 at 10:02
AnonymousLurkerAnonymousLurker
2007
asked Feb 21 at 10:02
AnonymousLurkerAnonymousLurker
2007
asked Feb 21 at 10:02
AnonymousLurkerAnonymousLurker
2007
2007
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The commands given with -c are executed after the first file is loaded. I guess that at that time, vimwiki is already initialized and asked for creation of the directory ~/vimwiki.
Use --cmd .... This commands are executed before vimrc is loaded. So the variable should be set at the time vimwiki is initializing.
Untested:
gvim --cmd "let g:vimwiki_list = [{'path': '$PWD/'}]" -c "normal ,ww"
So g:vimwiki_list is assigned before vimrc is sourced and ,ww is executed after the first file was loaded.
See :help --cmd and :help -c.
answered Feb 21 at 12:41
RalfRalf
3,0551317
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "599"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fvi.stackexchange.com%2fquestions%2f18981%2fcant-make-vimwiki-honor-setting-passed-via-command-line%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The commands given with -c are executed after the first file is loaded. I guess that at that time, vimwiki is already initialized and asked for creation of the directory ~/vimwiki.
Use --cmd .... This commands are executed before vimrc is loaded. So the variable should be set at the time vimwiki is initializing.
Untested:
gvim --cmd "let g:vimwiki_list = [{'path': '$PWD/'}]" -c "normal ,ww"
So g:vimwiki_list is assigned before vimrc is sourced and ,ww is executed after the first file was loaded.
See :help --cmd and :help -c.
answered Feb 21 at 12:41
RalfRalf
3,0551317
add a comment |
The commands given with -c are executed after the first file is loaded. I guess that at that time, vimwiki is already initialized and asked for creation of the directory ~/vimwiki.
Use --cmd .... This commands are executed before vimrc is loaded. So the variable should be set at the time vimwiki is initializing.
Untested:
gvim --cmd "let g:vimwiki_list = [{'path': '$PWD/'}]" -c "normal ,ww"
So g:vimwiki_list is assigned before vimrc is sourced and ,ww is executed after the first file was loaded.
See :help --cmd and :help -c.
answered Feb 21 at 12:41
RalfRalf
3,0551317
add a comment |
The commands given with -c are executed after the first file is loaded. I guess that at that time, vimwiki is already initialized and asked for creation of the directory ~/vimwiki.
Use --cmd .... This commands are executed before vimrc is loaded. So the variable should be set at the time vimwiki is initializing.
Untested:
gvim --cmd "let g:vimwiki_list = [{'path': '$PWD/'}]" -c "normal ,ww"
So g:vimwiki_list is assigned before vimrc is sourced and ,ww is executed after the first file was loaded.
See :help --cmd and :help -c.
answered Feb 21 at 12:41
RalfRalf
3,0551317
The commands given with -c are executed after the first file is loaded. I guess that at that time, vimwiki is already initialized and asked for creation of the directory ~/vimwiki.
Use --cmd .... This commands are executed before vimrc is loaded. So the variable should be set at the time vimwiki is initializing.
Untested:
gvim --cmd "let g:vimwiki_list = [{'path': '$PWD/'}]" -c "normal ,ww"
So g:vimwiki_list is assigned before vimrc is sourced and ,ww is executed after the first file was loaded.
See :help --cmd and :help -c.
answered Feb 21 at 12:41
RalfRalf
3,0551317
answered Feb 21 at 12:41
RalfRalf
3,0551317
answered Feb 21 at 12:41
RalfRalf
3,0551317
answered Feb 21 at 12:41
RalfRalf
3,0551317
3,0551317
add a comment |
add a comment |
Thanks for contributing an answer to Vi and Vim Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fvi.stackexchange.com%2fquestions%2f18981%2fcant-make-vimwiki-honor-setting-passed-via-command-line%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
