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 20:57:25 -0600 [thread overview]
Message-ID: <CAAXzdLV2-Jmj+17YWDDSt76sDBRgLRa=no7zusmLg4tS0OypYg@mail.gmail.com> (raw)
In-Reply-To: <CALKJ+EvjssWupZ=Zns4zhycMXePwzpa6edVqbKBSWixe76onPg@mail.gmail.com>
On Sat, Jan 4, 2020 at 8:13 PM Trey Ethan Harris wrote:
> 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.
which would have been nice if my question was, "how to I configure my software
to wrap without inserting newlines?" but the question actually was, how to enter
newline that are removed in the output.
> ...and which, again, has nothing to do with Org whatsoever—it’s 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!)
yes, and I would have never made this point had you not insisted on starting an
off topic conversation.
> You said you want to “deal with” long links in Org. But your example HTML file
> linked to has nothing to do with Org syntax AFAICT—it’s just a file that
> happens to horizontally scroll when viewed as source on GitHub.
again you seems to be totally missing the point here.
i can set my paragraphs to be single line as youve suggested. and with org mode
files, even GitHub will render them correctly.
But as you can imagine, I dont only work with Org Mode files. I also work with
Python files, Go, Dart and a number of other types. And none of these other
types get the wrapping on GitHub. So in order to have the best result across all
my files, I prefer to do hard wrapping. That is easy enough to handle in all
cases except the one ive presented in the original post.
The one that youve yet to address directly. Now again I dont wish to discuss or
get into further the merits of hard wrapping vers soft. So perhaps you can take
that discussion elsewhere and keep this on topic.
Next we know you will say why someone is using spaces over tabs, or emac over
vim, or red over blue bikeshed. Stop.
next prev parent reply other threads:[~2020-01-05 2:57 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
2020-01-05 0:59 ` Steven Penny
2020-01-05 2:13 ` Trey Ethan Harris
2020-01-05 2:57 ` Steven Penny [this message]
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='CAAXzdLV2-Jmj+17YWDDSt76sDBRgLRa=no7zusmLg4tS0OypYg@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).