From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Steven Penny <svnpenn@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Trey Ethan Harris <treyharris@gmail.com>
Subject: Re: Long links
Date: Sun, 5 Jan 2020 08:03:32 +0000 [thread overview]
Message-ID: <87y2umwcrx.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CAAXzdLV2-Jmj+17YWDDSt76sDBRgLRa=no7zusmLg4tS0OypYg@mail.gmail.com> (Steven Penny's message of "Sat, 4 Jan 2020 20:57:25 -0600")
On Saturday, 4 Jan 2020 at 20:57, Steven Penny wrote:
> 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.
As it may be. But maybe I'm missing the point as well. I do not see
what github's behaviour has to do with org mode's display of links
(angle brackets or not). Should you be asking github to change?
Your original post simply said you wished to wrap long lines and you
said "Does Org Mode have some way to deal with this?". Trey gave you
one way: use visual-line-mode (which is also what I use and have done
for years). His response was on-topic.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.3-34-g2eee3c
next prev parent reply other threads:[~2020-01-05 8:03 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
2020-01-05 6:25 ` Adam Porter
2020-01-05 8:03 ` Fraga, Eric [this message]
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=87y2umwcrx.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=svnpenn@gmail.com \
--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 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.