-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
docs: More clean-ups (smoe:docs_man_adoc_20240813-2) #3110
Conversation
The error is not caused by this PR:
|
[Steffen Möller]
The error is not caused by this PR:
Yes, there is a race condition in the single-step test. I restarted the
test and now it succeeded.
I do unfortunately not have time to review these changes for a while. I
hope someone can have a look.
…--
Happy hacking
Petter Reinholdtsen
|
1531bb5
to
049b59f
Compare
@hansu , may I ask you? Should not be too bad. |
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.
What is CMS_buffer.eps?
Please also remove the asterisks from linuxcncrsh.1.adoc:58 while you are at it :)
To use linuxcncrsh instead of a normal LinuxCNC GUI like AXIS or Touchy,
specify it in your INI file like this:
----
-*[DISPLAY]*
+[DISPLAY]
-*DISPLAY=linuxcncrsh*
+DISPLAY=linuxcncrsh
----
@@ -122,7 +122,7 @@ gscreen-gaxis has a sample custom theme that looks for certain named widgets and | |||
The Estop and machine-on buttons use different colors then the rest of the buttons so that they stand out. | |||
This is done in the handler file by giving them specific names an by adding specific commands in the theme's gtkrc file. | |||
For some info on GTK theming (The sample theme uses the pixmap theme engine), see: | |||
https://wiki.gnome.org/Attic/GnomeArt/Tutorials/GtkThemes[GTK Themes], | |||
https://wiki.gnome.org/Attic/GnomeArt/Tutorials/GtkThemes[GTK Themes], |
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.
This space should stay
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.
This one is still remaining
It is the DIA (https://en.wikipedia.org/wiki/Dia_(software))-generated post script from which https://github.com/LinuxCNC/linuxcnc/blob/master/docs/src/code/CMS_buffer.png is derived. The EPS file itself is not used. |
Looking at the bad quality of the PNG, it may be worthwhile to have a second look at my idea to remove the EPS. |
Would changing the EPS to an SVG work? (Do our tools display SVG? Web browsers display them by default) |
|
…lost. Transformed the .eps to an editable .svg and exported the PNG in a 300 dpi resolution.
b6be53d
to
0efb01b
Compare
|
The error in debian:bookworm is triggered by the tests:
Tend to think that this PR is not triggering this. |
@hansu, this patch needs to build and thus I want to push something else that is somehow trivial but useful. Concerning that blank that you wanted to be added back in, is this still a thing? I truly think that it would be wrong to add, and since I am likely to make that mistake (if any) again with the upcoming changes, please kindly explain what your concern is. |
Simply look here: https://linuxcnc.org/docs/devel/html/gui/gscreen.html#_overview This
would turn into
|
No, it would not? I mean, have you seen that happening? Definitely does not happen in the vscode preview. The patch intends to remove the blank that is still followed by a newline, not also the newline. We have lines ending with commas or periods all the time that have proper white space following in the HTML/pdf. I yet fail to see (and would want to understand) why is this now special. ?´+ü´[ <- baby-cat just contributed some extra characters ] If you do not ultimately mind, please just accept the patch. I'll make a $100 donation to FreeCAD if there is no white space in the PDF after that comma ... and likely spend the rest of the year to find the bug in the autodoc parser. |
You are right, sorry. I missed the line break and thought just Github editor did the line break 😇 |
I took my local version of the #3066 and rebased it against master. Added another patch to remove empty blanks at the end of lines. Now looks clean, no exact idea what I did differently.
@petterreinholdtsen , @hansu , Please kindly review this one and then I see what I can do to save what is still important n #3066 .
Many thanks,
Steffen