-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
doc: more about nick, user, and name #1680
Conversation
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.
Also:
.. highlight:: ini
can be used to remove the usage of.. code-block:: ini
in the whole file, since we don't show Python code in that particular file, but a lot ofini
-like code sample.
Might as well do that in another commit. This PR is too small. Only one nemesis to vanquish in this one, anyway—you need more to do! 😝
49f2256
to
4ad3928
Compare
@dgw I split in 2 commits, for the |
Oh, I thought doing the |
Lazyness? 😁 |
I removed that excuse by pushing a commit that does it for you. 😸 |
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.
Should be good now, with my added commit to get rid of .. code-block:: ini
everywhere.
746db38
to
12a2c41
Compare
#1628 doc-updating game too strong. 😆 Rebased. |
After we got a question about that on IRC, I thought it could be a good idea to improve the documentation for nick, user, and name.
Note: I'd like to have #1668 merged so the doc stop complaining about that stupid mistake I made.
Also:
.. highlight:: ini
can be used to remove the usage of.. code-block:: ini
in the whole file, since we don't show Python code in that particular file, but a lot ofini
-like code sample.