Replies: 5 comments
-
|
The dynamic summary lines generated by IntList can already exceed 79 columns due to appending register states, sometimes as many as three registers and some may list multiple values. So for that use case I wouldn't be opposed to just letting it (a single line) overflow the usual width. Maybe we could have a similar option in makelist as the sort-as IDs, so the default summary base line is the first nonempty line after the header and there could be some way to specify a (shorter) legacy summary base line after the normal one or in the header? |
Beta Was this translation helpful? Give feedback.
-
|
I think the text in the generated LST files should stay under 80 characters per line for readability purposes. But, we could easily add a simple *nix trick. When that first line ends in a I was also thinking about doing a search/replace on the title for either |
Beta Was this translation helpful? Give feedback.
-
|
If the header contained the expanded title for the Then, makelist would use everything up to the first Or it could word-wrap (leaving out the |
Beta Was this translation helpful? Give feedback.
-
|
I'd rather spell out any dashes you want to include, with optional whitespace before or after the |
Beta Was this translation helpful? Give feedback.
-
|
Maybe using the backslash continuation for both source and compiled files is best. Then just let IntList or other readers collapse the continued line into a single line if they so desire. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
While performing some typographic corrections, I was reminded that some Interrupt Titles have very long descriptions. Often this leads to words being abbreviated. Such abbreviations are often non-standard. For example, look at the description for Netware 21C706.
That text is as long as possible without causing a line-wrap when viewed in 80 columns.
The problem is the abbreviation "APPLICTN." If a user is simply searching the text for "application thresholds", this entry would never appear. That abbreviated phrase only appears in the title and not the body of the entry.
But if the word in the description is not abbreviated, the title would need to be more than one line. A parser (like the upcoming makehtml) could contain a list of words and expand them on-the-fly when generating the HTML. However, this would not help anyone performing a direct text search on the LST files.
Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions