Skip to content
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

ConfigHelp.md: Fix format/rendering issue in documentation #17

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

cyber-g
Copy link

@cyber-g cyber-g commented Jul 20, 2021

There is a small formatting/rendering issue for the markdown ConfigHelp.md documentation file.

Some sections are highlighted by div tags (example : <div id='id-section1'/>)
These tags are currently directly followed by subsection titles (example : ## [PARAMETERS] ##)

Issue : the subsection title is not properly rendered on the web interface.

Solution : There should be an empty line after those tags for having a proper rendering of the subsection titles.

This PR fixes this rendering issue by adding the appropriate empty lines after the div tags.

sberl and others added 8 commits February 3, 2021 16:55
Updated to use pyalsaaudio 0.9.0. Some of the parameters to alsaaudio.PCM
have changed and some calls have been deprecated.

Added find_alsa_devices.py script to show a list of all the audio capture
devices on the system.
…it is available via HTTPS. So needed to change the decision of which to use when.
Code was overwriting the users selection of log file format.
Remove the code that does that so the user can choose.
NOAA has moved around their data repository so need to change
algorithm to fetch data 2017 or newer via FTP instead of HTTP
@sberl
Copy link

sberl commented Jul 20, 2021

Hey cyber-g. Thanks for the fix. Eric is kind of on break from maintaining this code.
The current development activity is over at https://github.com/sberl/supersid.
If it isn't too much trouble, could you open the PR over there?

Thanks.

@cyber-g
Copy link
Author

cyber-g commented Jul 20, 2021

Sure !
I will proceed to the PR at https://github.com/sberl/supersid any time soon ; I guess I will have to fetch the available new commits before.
Should be done in the next few days.
Best regards

@cyber-g
Copy link
Author

cyber-g commented Jul 21, 2021

Should I close this PR since it is continued on fork of @sberl ?
(sberl/supersid#1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants