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
some help tags about function details are inconsistent #6849
Labels
Comments
This command outputs all the help tags matching the pattern `-function*-details`:
pu=getcompletion('-function*-details', 'help')
job-functions-details
sign-functions-details
test-functions-details
popup-function-details
assert-functions-details
channel-functions-details
terminal-function-details
Notice that all the tags use the plural of the word "function":
job-functions-details
^
sign-functions-details
^
test-functions-details
^
assert-functions-details
^
channel-functions-details
^
Except these 2:
popup-function-details
^
✘
terminal-function-details
^
✘
This is inconsistent.
This comes from adding "-details" after "some-functions". But it reads
strange, perhaps we should follow the last two. Not sure though.
Opinions?
If you run this global command while reading `:h eval`:
:g/are documented/p
You get this output:
assert_ functions are documented here: |assert-functions-details|
ch_ functions are documented here: |channel-functions-details|
job_ functions are documented here: |job-functions-details|
popup_ functions are documented here: |popup-functions|.
prop_ functions are documented here: |text-prop-functions|.
sign_ functions are documented here: |sign-functions-details|
term_ functions are documented here: |terminal-function-details|
test_ functions are documented here: |test-functions-details|
Notice that all the lines end with a tag name using the keyword "details" and without a dot at the end:
assert_ functions are documented here: |assert-functions-details|
^-----^
ch_ functions are documented here: |channel-functions-details|
^-----^
job_ functions are documented here: |job-functions-details|
^-----^
sign_ functions are documented here: |sign-functions-details|
^-----^
term_ functions are documented here: |terminal-function-details|
^-----^
test_ functions are documented here: |test-functions-details|
^-----^
Except these 2:
prop_ functions are documented here: |text-prop-functions|.
^^
details is missing; dot is superfluous
popup_ functions are documented here: |popup-functions|.
^^
details is missing; dot is superfluous
This is also inconsistent.
OK, let's remove the dots.
---
The following patch tries to address these issues:
```diff
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index a2e1af919..0f7e14ec4 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -7607,7 +7607,7 @@ perleval({expr}) *perleval()*
< {only available when compiled with the |+perl| feature}
-popup_ functions are documented here: |popup-functions|.
+popup_ functions are documented here: |popup-functions-details|
I prefer using popup-functions here, as it gives an overview of the
functions, before going into details.
…--
Q: Is selling software the same as selling hardware?
A: No, good hardware is sold new, good software has already been used by many.
/// Bram Moolenaar -- Bram@Moolenaar.net -- 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 ///
|
I guess it would work too. Using the last two as a template for the other ones would bring the whole set of tags more in line with all the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This command outputs all the help tags matching the pattern
-function*-details
:Notice that all the tags use the plural of the word "function":
Except these 2:
This is inconsistent.
If you run this global command while reading
:h eval
:You get this output:
Notice that all the lines end with a tag name using the keyword "details" and without a dot at the end:
Except these 2:
This is also inconsistent.
The following patch tries to address these issues:
The text was updated successfully, but these errors were encountered: