From: Trey Ethan Harris <treyharris@gmail.com>
To: Steven Penny <svnpenn@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Long links
Date: Sat, 4 Jan 2020 19:45:06 -0500 [thread overview]
Message-ID: <CALKJ+Ev2WhufsQdu5vNziNXcLMMEqHj8WZ4e2Mi-AmOCq=9KVg@mail.gmail.com> (raw)
In-Reply-To: <CAAXzdLV7qVScFARvgE1bKtS651yecLnQynNprUEh-Q-Go6H7RA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2277 bytes --]
On Sat, Jan 4, 2020 at 19:23 Steven Penny <svnpenn@gmail.com> wrote:
> On Sat, Jan 4, 2020 at 6:18 PM Trey Ethan Harris wrote:
> > I think you did not explain your issue clearly, then—on GitHub, long
> lines and
> > long links are displayed perfectly, as this example with a 434-character
> line
> > and your originally-mentioned link shows, with no horizontal scrolling
> and no
> > special styling:
> >
> > https://gist.github.com/treyharris/fcfb2558806e35ffc8d3dd4502a06c39
>
> If you had browsed beyond even the most basic example, you would see that
> your
> point falls apart:
>
> https://github.com/cup/autumn/blob/master/docs/append-to-array/index.html
Uh... that’s an HTML file—this is the emacs-orgmode mailing list. And
viewing that page as rendered HTML in a browser, there’s no horizontal
scrolling I see (and doesn’t appear to be with your styles as rendered at
https://cup.github.io/autumn/append-to-array/). I was asking for an example
of an Org mode file showing the issue that’s concerning you, not just proof
that GitHub sometimes does horizontal scrolling.
If you’re asking about long lines in general that could be generated as
export from Org-mode to any other format, such as Org *into* HTML, and then
want to limit the lengths of the lines of the exported document code
generated, in characters—and not what is displayed in width as pixels—then
I don’t understand why you’d even be looking at Org-mode’s own link syntax.
Line breaks in an Org file do not, in the general case, propagate into
exported formats (except when line breaks are significant, like in source
blocks). So successfully line-breaking in the middle of a URL in Org
wouldn’t necessarily generate a line-broken URL in the resulting HTML (or
TeX or PDF, source or rendered).
In any case, there will be no single solution to this—any ox library for
Org export you use will have to be modified if they don’t handle
line-breaks the way you want.
If you’re planning on including verbatim Org source examples _in_ the
generated HTML (as you are currently doing for comparing programming
languages), that’s the case where a long Org source line might bleed
visibly into the final rendered output. Are you?
[-- Attachment #2: Type: text/html, Size: 3258 bytes --]
next prev parent reply other threads:[~2020-01-05 0:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 20:51 Long links Steven Penny
2019-12-30 2:08 ` Nicolas Goaziou
2019-12-30 4:13 ` Steven Penny
2019-12-30 8:55 ` Nicolas Goaziou
2020-01-04 15:36 ` Steven Penny
2020-01-04 17:44 ` Nicolas Goaziou
2020-01-04 21:58 ` Steven Penny
2020-01-04 22:35 ` Trey Ethan Harris
2020-01-04 22:56 ` Steven Penny
2020-01-04 23:08 ` Trey Ethan Harris
2020-01-04 23:26 ` Steven Penny
2020-01-05 0:18 ` Trey Ethan Harris
2020-01-05 0:23 ` Steven Penny
2020-01-05 0:45 ` Trey Ethan Harris [this message]
2020-01-05 0:59 ` Steven Penny
2020-01-05 2:13 ` Trey Ethan Harris
2020-01-05 2:57 ` Steven Penny
2020-01-05 6:25 ` Adam Porter
2020-01-05 8:03 ` Fraga, Eric
2020-01-05 14:02 ` Steven Penny
2020-01-05 16:08 ` Eduardo Ochs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALKJ+Ev2WhufsQdu5vNziNXcLMMEqHj8WZ4e2Mi-AmOCq=9KVg@mail.gmail.com' \
--to=treyharris@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=svnpenn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.