From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Read only org view mode
Date: Mon, 24 Jan 2022 13:58:15 +0100 [thread overview]
Message-ID: <Ye6iZ915+1IjAIMt@maokai> (raw)
In-Reply-To: <CAKuG=vsLF33FTmy1Bu20KXH5GPc-zpKDNrgQ0nsJ6yrEP2iNqg@mail.gmail.com>
On Mon, Jan 24, 2022 at 11:40:05AM +0000, Neil Jerram wrote:
> On Mon, 24 Jan 2022, 11:14 Russell Adams, <RLAdams@adamsinfoserv.com> wrote:
>
> > Why not just do an ASCII export to a temporary read only buffer for
> > viewing?
>
> Do you mean that you're agreeing with the concept, but finding the
> implementation unnecessarily complicated?
I'm not being negative about the concept. I'm asking if the poster had
considered using the built-in tools before creating another new
library.
I did a short look at the site and the assertion "view org with less
markup", and that was my first impression.
I had two thoughts. The first was if the markup is a problem and you
want a read only view, why not use the built in ascii export to a
buffer and view that buffer? I just hit C-c C-e t A and M-x
read-only-mode and was able to navigate my ascii org file as a read
only buffer.
Second thought was that Org's syntax was supposed to minimize the
markup so it didn't negatively impact reading. Maybe the poster is
identifying a pain point we should be aware of as a community, ie:
that too much markup makes it hard to read.
My impression is only property drawers and source blocks are
potentially visually loud compared to the other markup. Timestamps are
pretty minimal and links already only show a descriptive text instead
of the full [[]] syntax.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
prev parent reply other threads:[~2022-01-24 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 7:19 Read only org view mode Arthur Miller
2022-01-24 6:20 ` Marcin Borkowski
2022-01-24 10:30 ` Neil Jerram
2022-01-24 11:11 ` Russell Adams
2022-01-24 11:40 ` Neil Jerram
2022-01-24 12:58 ` Russell Adams [this message]
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=Ye6iZ915+1IjAIMt@maokai \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.org \
/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).