emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [longlines] (was: example paper written in org completely)
Date: Fri, 18 Jun 2021 11:19:36 -0400	[thread overview]
Message-ID: <CAF-FPGPVx-5poauKzTwN2cb5Oo7J3h8Dutr7M4z4g=2xHkQLpw@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETrH3E1_udDBCxC3OR+ejKBW5Spa4NvZNVH-+rgEZX=hRQ@mail.gmail.com>

I recently switched to one-sentence-per-line + visual-line-mode.

On Fri, Jun 18, 2021 at 11:00 AM John Kitchin <jkitchin@andrew.cmu.edu> wrote:
>
> I use visual-line-mode. It almost always works fine for me.
>
> On Fri, Jun 18, 2021 at 10:38 AM Uwe Brauer <oub@mat.ucm.es> wrote:
>>
>> >>> "ESF" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>> > On Friday, 18 Jun 2021 at 13:55, Uwe Brauer wrote:
>> >> Right, fair enough. I thought it was MS Office or something like this.[1]
>>
>> > Yeah; I avoid that problem mostly by using ODT export in org.
>>
>> > Sometimes, if I have to work on an actual document that LibreOffice or
>> > gnumeric cannot handle, I access our institution's systems using
>> > rdesktop and/or a web interface.  Luckily, I only have to the latter
>> > once every few months at most.
>>
>> Coming back to your original post. I finally downloaded it and had a
>> quick look at its source org file.
>>
>> You are using longlines (that is now auto-fill after 70 chars).
>>
>> I never found a longline mode I liked and that is why I stick to good
>> old auto-fill with 70 chars.
>>
>> I wounder what you use to display the file (I am using a either a 14
>> inch Thinkpad X1 or 13inch MacBookAir, so maybe that is the issue here).
>>
> --
> John
>
> -----------------------------------
> Professor John Kitchin (he/him/his)
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>


  reply	other threads:[~2021-06-18 15:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 12:06 example paper written in org completely Eric S Fraga
2021-06-17 12:51 ` Juan Manuel Macías
2021-06-17 13:38 ` Greg Minshall
2021-06-17 15:06   ` Eric S Fraga
2021-06-17 15:11   ` Eric S Fraga
2021-06-17 16:33   ` Uwe Brauer
2021-06-17 16:40     ` Eric S Fraga
2021-06-17 19:54       ` Uwe Brauer
2021-06-18  8:02         ` Eric S Fraga
2021-06-18 11:55           ` Uwe Brauer
2021-06-18 12:46             ` Eric S Fraga
2021-06-18 14:38               ` [longlines] (was: example paper written in org completely) Uwe Brauer
2021-06-18 15:00                 ` John Kitchin
2021-06-18 15:19                   ` Bruce D'Arcus [this message]
2021-06-18 16:30                     ` [longlines] Uwe Brauer
2021-06-24 22:09                       ` [longlines] Haider Rizvi
2021-06-18 16:38                     ` [longlines] Uwe Brauer
2021-06-18 15:23                 ` [longlines] Eric S Fraga
2021-06-18 23:26             ` example paper written in org completely Tim Cross
2021-06-19  9:58               ` Jeremie Juste
2021-06-19 13:12                 ` Eric S Fraga
2021-06-19 15:58                 ` Samuel Banya
2021-06-17 14:40 ` Samuel Banya
2021-06-17 16:31 ` Christopher Dimech
2021-06-17 16:42   ` Eric S Fraga
2021-06-17 17:04     ` Christopher Dimech
2021-06-17 17:19       ` Christopher Dimech
2021-06-18  8:04         ` Eric S Fraga
2021-06-18 13:45           ` Christopher Dimech
2021-06-18 23:02             ` Tim Cross
2021-06-19  0:21               ` Christopher Dimech

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='CAF-FPGPVx-5poauKzTwN2cb5Oo7J3h8Dutr7M4z4g=2xHkQLpw@mail.gmail.com' \
    --to=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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).