From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Alternatives to inlinetasks? [was: Problems created by inlinetasks in agenda views]
Date: Tue, 24 Apr 2018 09:01:46 -0700 [thread overview]
Message-ID: <87fu3klhjp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAFyQvY1iHPKcXLa+Bfr7Y9096mzv5pLvnFHFOFrPxCTrnjA=YA@mail.gmail.com
Kaushal Modi <kaushal.modi@gmail.com> writes:
> On Mon, Apr 23, 2018, 5:35 PM Eric Abrahamsen
> <eric@ericabrahamsen.net> wrote:
>
> Would there be any consideration for an inline syntax that looks
> more
> like a link? Personally, when I want inline TODOs, I want them
> because
> there's a particular chunk of text that I need to do something
> with.
> What about something that looks like:
>
> In 2005 there were approximately [[TODO: Verify this; SCHEDULED:
> <tomorrow>; :statistics:][4,500]] Confucius Institutes in
> operation
> worldwide.
>
> How would you distinguish between regular links and such inline TODO's
> when the "link" portion is hidden?
I guess I wouldn't, personally, I'd just use the agenda to interact with
the TODOs. But there could be a separate option allowing users to
control the visibility of inline TODOs independently.
I dunno, I was just throwing this out there :)
> Would footnotes serve better? (I'm not a consumer of inline todos
> (yet?) so consider this suggestion with a grain of salt :))
That's not a bad idea either! I do like links' ability to connect to a
specific run of text, but this would also work.
Eric
next prev parent reply other threads:[~2018-04-24 16:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 14:24 Problems created by inlinetasks in agenda views Alain.Cochard
2018-04-16 12:08 ` Nicolas Goaziou
2018-04-16 14:01 ` Eric S Fraga
2018-04-16 16:39 ` Nicolas Goaziou
2018-04-16 17:01 ` Eric S Fraga
2018-04-16 17:25 ` Berry, Charles
2018-04-16 17:33 ` Nicolas Goaziou
2018-04-23 13:50 ` Alternatives to inlinetasks? [was: Problems created by inlinetasks in agenda views] Alain.Cochard
2018-04-23 14:21 ` Eric S Fraga
2018-04-23 16:03 ` Carsten Dominik
2018-04-23 21:08 ` Nicolas Goaziou
2018-04-23 21:31 ` Eric Abrahamsen
2018-04-24 11:47 ` Kaushal Modi
2018-04-24 16:01 ` Eric Abrahamsen [this message]
2018-04-24 20:22 ` Rasmus
2018-04-25 5:43 ` Carsten Dominik
2018-04-26 23:34 ` Bastien
2018-04-27 7:27 ` Eric S Fraga
2018-04-27 7:46 ` Bastien
2018-04-27 7:57 ` Eric S Fraga
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=87fu3klhjp.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).