From: Steven Penny <svnpenn@gmail.com>
To: Trey Ethan Harris <treyharris@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Long links
Date: Sat, 4 Jan 2020 17:26:38 -0600 [thread overview]
Message-ID: <CAAXzdLWy57xwJuWVwHovdg4c17_EOxihxb3fvTYi35vmPHBT8w@mail.gmail.com> (raw)
In-Reply-To: <CALKJ+Eusqs1v50tSr1SqGo2_mpw=USnu+G5yV+PoNX-hxDUJ4g@mail.gmail.com>
On Sat, Jan 4, 2020 at 5:08 PM Trey Ethan Harris wrote:
> But my larger point was that for me, _stored_ line length (as opposed to
> displayed line length) should be dictated by export, not for some arbitrary
> purpose.
I dont think you understand, I want what I work on and publish to be readable.
On my own system thats easy enough, and your method would work fine. But if you
publish to GitHub or other sites, they have their own view of what a proper
display should be.
For example with GitHub, you dont get to choose tab width, and you dont get to
choose wrapping modes. GitHub uses 8 width tabs, and doesnt wrap at all. So if
you have any long lines you have to horizontal scroll, and if you dont like tab
width then you need to use spaces.
Granted I could just set some user CSS, but then anyone else visiting my pages
wont get the benefit of that.
I would please ask that you not comment further on this off topic discussion.
Unless you have an on topic comment regarding breaking long links I am not
interested, thank you.
next prev parent reply other threads:[~2020-01-04 23:26 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 [this message]
2020-01-05 0:18 ` Trey Ethan Harris
2020-01-05 0:23 ` Steven Penny
2020-01-05 0:45 ` Trey Ethan Harris
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAXzdLWy57xwJuWVwHovdg4c17_EOxihxb3fvTYi35vmPHBT8w@mail.gmail.com \
--to=svnpenn@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=treyharris@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).