You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically I'm copying the style of the parameter names in the function header, by doing this I can visually distinguish more easily when I am referring to a parameter or when I am referring to simple code.
What I don't like about my solution is that I have to use the @p{paramName} syntax instead of @p paramName, which makes comments longer and slightly harder to read.
Do you think it would be possible to implement this change directly in doxygen-awesome-css?
Is there a way to continue using the @p paramName syntax?
The text was updated successfully, but these errors were encountered:
parmi93
changed the title
Changing the style of the @p command
[Feature Request] Changing the style of the @p command
Sep 23, 2024
Unfortunately it seems like both @p and @c are just rendering to <code> blocks in HTML. I don't think that there is a way to distinguish them based on a CSS rule.
Please consider opening a PR at doxygen/doxygen for this feature.
I think that readability could be improved by introducing a different style for parameters (
@p
) and code (@c
) commands.For example, I made a small style change for the
@p
command with the following result:Dark mode:
Light mode:
Code documentation:
I added the following parameter in the
ALIASES
setting:p{1}=<code class="param">\1</code>
and
custom.css
in theHTML_EXTRA_STYLESHEET
setting:Basically I'm copying the style of the parameter names in the function header, by doing this I can visually distinguish more easily when I am referring to a parameter or when I am referring to simple code.
What I don't like about my solution is that I have to use the
@p{paramName}
syntax instead of@p paramName
, which makes comments longer and slightly harder to read.Do you think it would be possible to implement this change directly in
doxygen-awesome-css
?Is there a way to continue using the
@p paramName
syntax?The text was updated successfully, but these errors were encountered: