On Sun, Mar 27, 2016 at 12:52 AM, Bram Moolenaar <[email protected]> wrote:
>
> Gary Johnson wrote:
>
>> I read ":help packages" and ":help add-package", trying to get a
>> better understanding of how this all works, and had a few comments.
>> Vim version is 7.4.1655.
>
> Thanks. The changes after changes may have left some confusing text
> behind.
>
>>
>> * repeat.txt, line 484
>>
>> Note that the files under "pack/foo/opt" or not loaded
>> automatically, only the
>>
>> The "or" should be "are".
>>
>> * repeat.txt, line 519
>>
>> This could be done inside always.vim, if some conditions are met.
>> Or you
>>
>> There is no other mention of always.vim. I have no idea what
>> that file is for or where it should go.
>
> I'll remove always.vim, we don't need it.
>
>> * $VIMRUNTIME/pack/dist
>>
>> The matchit.vim plugin is now at
>> $VIMRUNTIME/pack/dist/opt/matchit/plugin/matchit.vim. I assume
>> that the "dist" directory is for optional plugins (non-optional
>> plugins would just go under $VIMRUNTIME) that come standard with
>> the Vim distribution. The "dist" directory is not documented
>> anywhere that I can find.
>
> It's just a name. :packadd looks in pack/*/opt.
>
>> * Installing the matchit plugin
>>
>> ":help matchit-install" recommends adding the line
>>
>> packadd matchit
>>
>> to one's vimrc file. As I wrote in another thread, I think it
>> would be better to recommend using
>>
>> packadd! matchit
>>
>> so that when troublshooting a problem by starting Vim with the
>> --noplugin option argument, the matchit plugin is not loaded
>> either.
>
> Already changed but didn't update runtime files yet.
>
>> * Package help files
>>
>> It seems that package help files could go into either
>> pack/*/start/doc or pack/*/opt/doc. Is there a preferred
>> location?
>
> The help file must be under the same directory as the plugin, so that
> when :packadd adds that directory to 'runtimepath' the help file can be
> found.
>
>> How do you add a local package help file? Is the
>> command
>>
>> :helptags ~/.vim/pack/mypack/start/myplugin/doc
>>
>> or is there something shorter that makes use of Vim's knowledge
>> of packages?
>
> When using a distributed package there should be no need to run
> :helptags. It should either come with a tags file or generate it when
> needed. If you add a plugin with docs yourself, you can run helptags
> for it.
>
> Pathogen has a command to run helptags on all directories in
> 'runtimepath'. Although that can be handy, it also may change tags
> files that you don't want to change. Esp. for packages that are from a
> repository, changing the tags file could create merge conflicts.
>
> Not sure if there is a way to help the user with this.
Hi Bram,
I'm working on translating this part into Japanese.
In addition to Gary's comment, I noticed a small error below while translating.
(see attached patch)
* "Error" should be "error".
An Error only causes sourcing the script where it
* In some places in repeat.txt, backtick(`) was used instead of bar(|)
like `:packadd`.
But almost quoted words seem to have its own helptag.
If there is a helptag, it should be quoted by bar so a user can jump it.
>
> --
> You cannot have a baby in one month by getting nine women pregnant.
>
> /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
> /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\ an exciting new programming language -- http://www.Zimbu.org ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
--
Takuya Fujiwara
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt
index c8624a2..9c26010 100644
--- a/runtime/doc/repeat.txt
+++ b/runtime/doc/repeat.txt
@@ -259,7 +259,7 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|.
Packages will be loaded only once. After this command
it won't happen again. When the optional ! is added
this command will load packages even when done before.
- An Error only causes sourcing the script where it
+ An error only causes sourcing the script where it
happens to be aborted, further plugins will be loaded.
See |packages|.
@@ -450,7 +450,7 @@ advantages over normal plugins:
easy to update.
- A package can contain multiple plugins that depend on each other.
- A package can contain plugins that are automatically loaded on startup and
- ones that are only loaded when needed with `:packadd`.
+ ones that are only loaded when needed with |:packadd|.
Using a package and loading automatically ~
@@ -511,7 +511,7 @@ From here it works like above.
Optional plugins ~
*pack-add*
-To load an optional plugin from a pack use the `:packadd` command: >
+To load an optional plugin from a pack use the |:packadd| command: >
:packadd foodebug
This searches for "pack/*/opt/foodebug" in 'packpath' and will find
~/.vim/pack/foo/opt/foodebug/plugin/debugger.vim and source it.
