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
Right now, Tidy adds newlines that aren't actually needed. Ideally, an option would exist to make Tidy only add a newline if it was actually necessary (to preserve the original meaning of the document, or to fix existing issues in a document).
The text was updated successfully, but these errors were encountered:
mjbshaw
changed the title
Add option to
Add option to prevent outputting unnecessary vertical whitespace
Feb 17, 2015
@mjbshaw you should pull and built the latest master branch, version 5.1.8 (2015.09.04) onward...
As can be seen in Issue #231 Tidy has a New Feature--vertical-space auto ;=))
Using your above Input and a config file of -
// New Feature - *NO* vertical space
vertical-space: auto
wrap: 0
show-info: no
tidy-mark: no
// not sure why you added this (as -access 1)
// accessibility-check: 1
which is more or less what you suggested... so am closing this issue...
Please feel free to re-open, or open a new issue...
For backward config capability --vertical-space yes and the default --vertical-space no will continue to produce what you may think of as additional unneccessary vertical space, but I guess it is much loved by many people...
Setting a yes, the so called tidy classic mode, will even add some more vertical space in specific certain circumstances...
Anyway, now you have an option for no vertical space ;=))
Input:
Output of
./tidy5 -access 1 --vertical-space f -wrap 0
:This is a feature request to add an option to tell Tidy to not add newlines that aren't necessary. So the output would be more like the following:
Right now, Tidy adds newlines that aren't actually needed. Ideally, an option would exist to make Tidy only add a newline if it was actually necessary (to preserve the original meaning of the document, or to fix existing issues in a document).
The text was updated successfully, but these errors were encountered: