-
Notifications
You must be signed in to change notification settings - Fork 84
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
No way to suppress hyphenation / inline URL #88
Comments
This appears to me to be an issue with the
In #89, you suggest using raw inlined ROFF as a workaround. But I don't see a way in ROFF itself to suppress hyphenation like this. Is there a particular mechanism you're thinking of? I also tried using the GNU
but they still end up wrapped and hyphenated when viewed in |
Hi,
|
Oh, cool. I didn't get that about the I agree with your point 3. I'll give this a try. Thanks. |
Well my original post doesn't say Thanks |
That I've implemented this in my "Ronn-NG" fork over at apjanke/ronn-ng#23 if you're interested in using it. |
Thanks; actually Emily is no longer an active project but I will keep your fork in mind when I next need manpages… |
I am attempting to use ronn for a manpage. It is doing everything I need EXCEPT: I need to include a URL in the manpage. The convention in manpages for this is to enter the URL in angle brackets, like http://example.com
In my current ronn file, it says:
The inner <> gets me an underline, and the outer <> gets me enclosing angle brackets. But unfortunately, when I look at my generated .1 file in man, I get:
This is catastrophic, it makes it appear the URL is http://emily-lang.org , which is incorrect.
The documentation for roff notes that there is a syntax for suppressing hyphenation on something (prefix with %). But it does not appear ronn exposes a way to access this.
Including URLs is a common thing for manpages. I would like to suggest ronn do one of the following to support this:
It appears that the man format also has some kind of standard "extension" for URLs. I cannot comment on whether it would make sense to leverage that.
The text was updated successfully, but these errors were encountered: