emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: stardiviner <numbchild@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org-drill edit feature request
Date: Fri, 28 Dec 2018 09:43:22 +0800	[thread overview]
Message-ID: <874layl939.fsf@gmail.com> (raw)
In-Reply-To: <CALjq+LbuzkE+uP7vmFQmeucCy5+ikX1VNRsxdcdJ49v0O5gXvw@mail.gmail.com>


Leu Zhe <lzhes43@gmail.com> writes:

I want org-drill can add a feature to auto pronounce the word. That's
standard functionality in word-drill Apps.

> Hi,
>
> Making drill editing seems be very painful by the current way
> org-drill offers.
> I make a lot of notes on most of the drilled entries, as for now,
> 1). press e (or other key to reveal the collapsed headlines) , e
> twice to go back to the original buffer.
> 2) add notes. (Even more keys pressing: if i collapsed the headlines
> before calling org-drill, i need to press tab to show all the
> contents at current headline.)
> 3) call org-drill-resume to go back.
>
> I would like to consider more intuitive ways to edit the drill
> entries. How do you think the workflow below?
> 1) press e to switch to edit mode like "helm-swoop", which keeps
> exactly same narrow, child headline showing as before.
> 2) add the notes.
> 3) Ctrl-c Ctrl-s to resume.
>
> Do you think my workflow is more reasonable?
> And i would like to hear more advices about the idea above. Thanks.
>
> LLCC


--
[ stardiviner ]
       I try to make every word tell the meaning what I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

  reply	other threads:[~2018-12-28  2:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 13:49 Org-drill edit feature request Leu Zhe
2018-12-28  1:43 ` stardiviner [this message]
2019-01-02 16:03   ` John Kitchin
2019-01-03 12:17     ` stardiviner

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=874layl939.fsf@gmail.com \
    --to=numbchild@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
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).