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

now the div are span for the kw in the listings #1190

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

Iximiel
Copy link
Member

@Iximiel Iximiel commented Jan 29, 2025

Description

This is the same tiny bit I have set up in a PR for Plumed2HTML.

The problem is that the div elements in the listing of the plumed examples in the manual causes extra new lines when copy-pasting the plumed examples.

for example

dist: DISTANCES ATOMS1=1,300 ATOMS2=1,400 ATOMS3=1,500

gets pasted as:

dist: DISTANCES ATOMS1
=1,300 ATOMS2
=1,400 ATOMS3
=1,500

I do not know if is the keyword element or the tooltip that pops up, but using to span will solve that problem (at least on Firefox).

Target release

I would like my code to appear in release v2.9

Type of contribution
  • changes to code or doc authored by PLUMED developers, or additions of code in the core or within the default modules
  • changes to a module not authored by you
  • new module contribution or edit of a module authored by you
Copyright
  • I agree to transfer the copyright of the code I have written to the PLUMED developers or to the author of the code I am modifying.
  • the module I added or modified contains a COPYRIGHT file with the correct license information. Code should be released under an open source license. I also used the command cd src && ./header.sh mymodulename in order to make sure the headers of the module are correct.
Tests
  • I added a new regtest or modified an existing regtest to validate my changes.
  • I verified that all regtests are passed successfully on GitHub Actions.

@carlocamilloni carlocamilloni merged commit c4fee1a into plumed:v2.9 Jan 29, 2025
13 of 14 checks passed
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