emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Cauim de Souza Lima <cauimsouza@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Minor rendering issues in the Org Mode Compact Guide
Date: Sat, 17 Dec 2022 23:11:20 +0000	[thread overview]
Message-ID: <CAHFpVgHiZtBQ9U5CzJ1P1jGQVJhTGiP9uVdi9ttcP535urZkUg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]

Hi, Org mode maintainers,

While reading the compact guide, I found a couple of minor rendering issues:

   - Section 2.2 Visibility Cycling
   <https://orgmode.org/guide/Visibility-Cycling.html>: "Org uses just two
   commands, bound to TAB and *{{{kbd{S-TAB)}}}* to change the visibility
   in the buffer."
   - Section 5.2 Multi-state Workflow
   <https://orgmode.org/guide/Multi_002dstate-Workflow.html>: "You can use
   TODO keywords to indicate *@emph{sequential}* working progress states"
   - Section 8.1 Timestamps <https://orgmode.org/guide/Timestamps.html>:
   "Its presence causes entries to be shown on specific dates in the agenda
   (see *[BROKEN LINK: *The Weekly/daily Agenda]*)."
   - Section 8.4 Clocking Work Time
   <https://orgmode.org/guide/Clocking-Work-Time.html>: "The l key may be
   used in the agenda (see *[BROKEN LINK: *The Weekly/daily Agenda])* to
   show..."
   - Section 10.2 The Agenda Dispatcher
   <https://orgmode.org/guide/Agenda-Dispatcher.html>: "Create the
   calendar-like agenda (see *[BROKEN LINK: *The Weekly/daily Agenda]*)."

These issues seem to be present in the HTML and in the PDF versions of the
manual.

I'd be happy to fix the issues myself but I'd need pointers.

Thanks,
Cauim

[-- Attachment #2: Type: text/html, Size: 1870 bytes --]

next             reply	other threads:[~2022-12-18  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17 23:11 Cauim de Souza Lima [this message]
2022-12-18 14:46 ` Minor rendering issues in the Org Mode Compact Guide Ihor Radchenko

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=CAHFpVgHiZtBQ9U5CzJ1P1jGQVJhTGiP9uVdi9ttcP535urZkUg@mail.gmail.com \
    --to=cauimsouza@gmail.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

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).