-
Notifications
You must be signed in to change notification settings - Fork 620
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
Update docs/optlib #2032
Update docs/optlib #2032
Conversation
I see. THANK YOU VERY MUCH. |
Neutral voice is better. I didn't do so because I could not do in my English skill. If you are interested in improving the other parts of ctags in the long term, let me know. I cannot do much for you in rerun but I can help you to convert Elixir parser to mtable-regex based :-P. |
I will resume work with this in a few days. Thank you for the compliment! Although my English isn't so good, hope it serves you well! Thank you for the invitation! But I have to refuse right now due to internet availability issues. When that improves, I'll let you know! |
I see. |
:file:`.ctags` extension under the previously specified directories. If you have | ||
multiple parser definitions, put them in different files. | ||
To make easier the maintenance a parser defined using the options, you can put | ||
each language parser in a different options file. Universal-ctags doesn't |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SELF NOTE: each language parser => each parser
Though using natural voice is better, the changes improve the documents much. So I will merge this after modifying the change a bit. |
_roles
,_fields
,_extras
)In lines 1573 to 1575 and 1621 to 1626 and maybe others, I used the first person ("Here I will explain...") because the paragraphs were written that way, but in no way that means my person (@dreamtigers) is the voice doing the explanation. In any case, it should be @masatake, with their permission. If it's an issue, I can rewrite those sections to use a neutral voice.
Before merging this, I will open an issue to discuss some doubts I have with some sections. Should those doubts be resolved, I can commit the additional changes, and then this pull request can be merged successfully.