From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trey Ethan Harris Subject: Re: Long links Date: Sat, 4 Jan 2020 21:13:31 -0500 Message-ID: References: <5e0911cd.1c69fb81.3d5f3.0029@mx.google.com> <87mubazht9.fsf@nicolasgoaziou.fr> <87woa7uneq.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000085064c059b5b1754" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:58353) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1invQJ-0001H3-QT for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 21:13:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1invQH-0001Mf-5s for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 21:13:47 -0500 Received: from mail-lj1-x242.google.com ([2a00:1450:4864:20::242]:39452) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1invQG-0001Gu-N0 for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 21:13:45 -0500 Received: by mail-lj1-x242.google.com with SMTP id l2so47467096lja.6 for ; Sat, 04 Jan 2020 18:13:44 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Steven Penny Cc: emacs-orgmode@gnu.org --00000000000085064c059b5b1754 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jan 4, 2020 at 19:58 Steven Penny wrote: > On Sat, Jan 4, 2020 at 6:45 PM Trey Ethan Harris wrote: > > Uh... that=E2=80=99s an HTML file=E2=80=94this is the emacs-orgmode mai= ling list. > > My original post: > > https://lists.gnu.org/archive/html/emacs-orgmode/2019-12/msg00422.html > > was, and is still on topic. Yet you found a way to make 4 posts without > addressing the original post directly. I literally included the link mentioned in your first post in my example Org file to address the question of whether it would cause horizontal scrolling. I couldn=E2=80=99t more directly address the original post witho= ut inventing new syntax for software that doesn=E2=80=99t exist. > > And viewing that page as rendered HTML in a browser, there=E2=80=99s no > horizontal > > scrolling I see (and doesn=E2=80=99t appear to be with your styles as r= endered at > > https://cup.github.io/autumn/append-to-array/). > > You should perhaps respond to what ive actually said, rather than what yo= u > think > im saying. Again this page here: > > https://github.com/cup/autumn/blob/master/docs/append-to-array/index.html > > is an example of GitHub not wrapping and requiring horizontal scrolling. ...and which, again, has nothing to do with Org whatsoever=E2=80=94it=E2=80= =99s simply an existence proof that GitHub sometimes does horizontal scrolling, which is entirely irrelevant to anything having anything to do with Org. (If you make your browser window narrow enough or use a phone, even the RST, asciiDoc and other examples you gave will horizontal-scroll, too!) > > I was asking for an example of an Org mode file showing the issue that= =E2=80=99s > > concerning you, not just proof that GitHub sometimes does horizontal > scrolling. > > again, see original post for example problem: > > https://lists.gnu.org/archive/html/emacs-orgmode/2019-12/msg00422.html > You said you want to =E2=80=9Cdeal with=E2=80=9D long links in Org. But you= r example HTML file linked to has nothing to do with Org syntax AFAICT=E2=80=94it=E2=80=99= s just a file that happens to horizontally scroll when viewed as source on GitHub. None of those links in your first post have any Org syntax in them. And it=E2=80=99s not what the links point to=E2=80=94they are about JavaScript.= Org syntax has nothing to do with JavaScript. The links as given in the original post *themselves* are long=E2=80=94so I = assumed that was the point. But as I showed, that doesn=E2=80=99t matter in how the= y=E2=80=99re displayed in Emacs if you select the right display mode; and that doesn=E2= =80=99t matter in how they=E2=80=99re displayed on GitHub in an Org file (again, I = used exactly the very link you started the just-linked-to post with in my Org file). > > In any case, there will be no single solution to this=E2=80=94any ox li= brary for > Org > > export you use will have to be modified if they don=E2=80=99t handle li= ne-breaks > the > > way you want. > > it seems you didnt even read all the responses, some good suggestions wer= e > posted here: > > https://lists.gnu.org/archive/html/emacs-orgmode/2019-12/msg00423.html > I absolutely did read that=E2=80=94I read the entire thread before respondi= ng since it seemed that none of he suggestions thus far had actually worked. GitHub doesn=E2=80=99t deal with the =E2=80=9Cgood suggestions=E2=80=9D cor= rectly, so I didn=E2=80=99t include them in my first Gist posted. I tried them first=E2=80=94I not only= did read the mail you=E2=80=99re claiming I didn=E2=80=99t, I wrote a new Org f= ile to test the suggestions within before posting anything. But here=E2=80=99s a Gist displ= aying a rendered Org file using those =E2=80=9Cgood suggestions=E2=80=9D: https://gist.github.com/treyharris/9dd193a4a1e34f0ba1619e8b04aecff1 It doesn=E2=80=99t handle the link correctly, and, if you make it long enou= gh on a given line, the bare sliced-in-twain URL you must cut and paste and remove spaces from if you want to use the URL will still horizontally scroll. Since it doesn=E2=80=99t work on GitHub=E2=80=94which is where you said you= published to and care about=E2=80=94I=E2=80=99m mystified on how it=E2=80=99s a =E2=80= =9Cgood suggestion=E2=80=9D where my syntax is not. (No disrespect meant to Nicolas at all=E2=80=94they *were* g= ood suggestions, insofar as they were worth trying. But I tried them.) I answered suggesting a different course because I thought you cared about how it actually displayed, not how it might display if the software worked differently than it does. The other =E2=80=9Cgood suggestion=E2=80=9D was link abbreviations. My Gist= given above gives one of those as well, and that one, GitHub doesn=E2=80=99t even make = any attempt at=E2=80=94it just displays it as plain text. Note: if GitHub did deal with these =E2=80=9Cgood suggestions=E2=80=9D corr= ectly, it would display just =E2=80=9ClastIndexOf=E2=80=9D=E2=80=94just like my Gist does i= n its first hyperlink, except mine says =E2=80=9Clong link=E2=80=9D where that says =E2=80=9ClastI= ndexOf=E2=80=9D. But yet apparently that working example is *not* a =E2=80=9Cgood suggestion=E2=80= =9D, though, compared to the ones that don=E2=80=99t work. (If you generally find exampl= es that don=E2=80=99t work acceptable, you can just insert {{{dwim}}} into any plac= e in your file you want a link, and it=E2=80=99ll do what you mean, whatever tha= t is. It works great on every implementation that supports it!) If you are being incredibly clear and I=E2=80=99m being incredibly obtuse, fine=E2=80=94I=E2=80=99ll drop it and someone who can divine what the heck = you=E2=80=99re asking for can respond instead. Or, you can continue attacking me for not reading what you wrote when I literally included quoted material from you in a file I published to illustrate the issue. Be my guest. --00000000000085064c059b5b1754 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Jan 4, 2020 at 19:58 Steven Penny <svnpenn@gmail.com> w= rote:
On Sat, Jan 4, 2020 at 6:45 PM Trey Et= han Harris wrote:
> Uh... that=E2=80=99s an HTML file=E2=80=94this is the emacs-orgmode ma= iling list.

My original post:

https://lists.gnu.org/archive/= html/emacs-orgmode/2019-12/msg00422.html

was, and is still on topic. Yet you found a way to make 4 posts without
addressing the original post directly.

I literally included= the link mentioned in your first post in my example Org file to address th= e question of whether it would cause horizontal scrolling. I couldn=E2=80= =99t more directly address the original post without inventing new syntax f= or software that doesn=E2=80=99t exist.


> And viewing that page as rendered HTML in a browser, there=E2=80=99s n= o horizontal
> scrolling I see (and doesn=E2=80=99t appear to be with your styles as = rendered at
> https://cup.github.io/autumn/append-to-array/)= .

You should perhaps respond to what ive actually said, rather than what you = think
im saying. Again this page here:

https://github.com/cup/autu= mn/blob/master/docs/append-to-array/index.html

is an example of GitHub not wrapping and requiring horizontal scrolling.

...and which, again, has nothing to do with Org whatsoever=E2= =80=94it=E2=80=99s simply an existence proof that GitHub sometimes does hor= izontal scrolling, which is entirely irrelevant to anything having anything= to do with Org. (If you make your browser window narrow enough or use a ph= one, even the RST, asciiDoc and other examples you gave will horizontal-scr= oll, too!)


> I was asking for an example of an Org mode file showing the issue that= =E2=80=99s
> concerning you, not just proof that GitHub sometimes does horizontal s= crolling.

again, see original post for example problem:

https://lists.gnu.org/archive/= html/emacs-orgmode/2019-12/msg00422.html


=
You said you want to =E2=80=9C= deal with=E2=80=9D long links in Org. But your example HTML file linked to = has nothing to do with Org syntax AFAICT=E2=80=94it=E2=80=99s just a file t= hat happens to horizontally scroll when viewed as source on GitHub.

None of those links in your fir= st post have any Org syntax in them. And it=E2=80=99s not what the links po= int to=E2=80=94they are about JavaScript. Org syntax has nothing to do with= JavaScript.

The links a= s given in the original post *themselves* are long=E2=80=94so I assumed tha= t was the point. But as I showed, that doesn=E2=80=99t matter in how they= =E2=80=99re displayed in Emacs if you select the right display mode; and th= at doesn=E2=80=99t matter in how they=E2=80=99re displayed on GitHub in an = Org file (again, I used exactly the very link you started the just-linked-t= o post with in my Org file).


> In any case, there will be no single solution to this=E2=80=94any ox l= ibrary for Org
> export you use will have to be modified if they don=E2=80=99t handle l= ine-breaks the
> way you want.

it seems you didnt even read all the responses, some good suggestions were<= br> posted here:

https://lists.gnu.org/archive/= html/emacs-orgmode/2019-12/msg00423.html

<= div dir=3D"auto">I absolutely did read that=E2=80=94I read the entire threa= d before responding since it seemed that none of he suggestions thus far ha= d actually worked.

GitHu= b doesn=E2=80=99t deal with the =E2=80=9Cgood suggestions=E2=80=9D correctl= y, so I didn=E2=80=99t include them in my first Gist posted. I tried them f= irst=E2=80=94I not only did read the mail you=E2=80=99re claiming I didn=E2= =80=99t, I wrote a new Org file to test the suggestions within before posti= ng anything. But here=E2=80=99s a Gist displaying a rendered Org file using= those =E2=80=9Cgood suggestions=E2=80=9D:

It doesn=E2=80=99t handle the link correctly, and, if you make it long en= ough on a given line, the bare sliced-in-twain URL you must cut and paste a= nd remove spaces from if you want to use the URL will still horizontally sc= roll.

Since it doesn=E2= =80=99t work on GitHub=E2=80=94which is where you said you published to and= care about=E2=80=94I=E2=80=99m mystified on how it=E2=80=99s a =E2=80=9Cgo= od suggestion=E2=80=9D where my syntax is not. (No disrespect meant to Nico= las at all=E2=80=94they *were* good suggestions, insofar as they were worth= trying. But I tried them.)

I answered suggesting a different course because I thought you cared ab= out how it actually displayed, not how it might display if the software wor= ked differently than it does.

= The other =E2=80=9Cgood suggestion=E2=80=9D was link abbreviations. My Gist= given above
gives one of those as well, and that one, Git= Hub doesn=E2=80=99t even make any attempt at=E2=80=94it just displays it as= plain text.

Note:= if GitHub did deal with these =E2=80=9Cgood suggestions=E2=80=9D correctly= , it would display just =E2=80=9ClastIndexOf=E2=80=9D=E2=80=94just like my = Gist does in its first hyperlink, except mine says =E2=80=9Clong link=E2=80= =9D where that says =E2=80=9ClastIndexOf=E2=80=9D. But yet apparently that = working example is *not* a =E2=80=9Cgood suggestion=E2=80=9D, though, compa= red to the ones that don=E2=80=99t work. (If you generally find examples th= at don=E2=80=99t work acceptable, you can just insert {{{dwim}}} into any p= lace in your file you want a link, and it=E2=80=99ll do what you mean, what= ever that is. It works great on every implementation that supports it!)

If you are being incredibly= clear and I=E2=80=99m being incredibly obtuse, fine=E2=80=94I=E2=80=99ll d= rop it and someone who can divine what the heck you=E2=80=99re asking for c= an respond instead. Or, you can continue attacking me for not reading what = you wrote when I literally included quoted material from you in a file I pu= blished to illustrate the issue. Be my guest.
--00000000000085064c059b5b1754--