Again, very impressive.
I do some of this with drawers but there could indeed be much more
support built-in for such aspects. Navigating drawers in org mode
should be easier.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78
The other aspects I find very useful are: 1) there is a display list so I
can see all the editmarks and jump to them. That way, in a proposal for
example I can see if there are any residual marks that should be removed.
2) when I make a pdf, they are converted to a list of todo items at the
front,
On Tuesday, 5 Nov 2019 at 07:49, John Kitchin wrote:
> I use it when editing papers mostly. The main difference is I can put
> them inline {>~ @jk here is a comment.~<} in a paragraph.
Very interesting. The inline aspect can be quite useful. Thanks for
the description!
--
Eric S Fraga via Em
I use it when editing papers mostly. The main difference is I can put
them inline {>~ @jk here is a comment.~<} in a paragraph. I use them to
mark {>.tpyos.<}, text for {>-deletion-<} removal, or {>+insertion+<},
{y>highlighted text writes:
> On Monday, 4 Nov 2019 at 15:14, John Kitchin wrote:
>
On Monday, 4 Nov 2019 at 15:14, John Kitchin wrote:
> I have been exploring the use of something I call editmarks for this
Out of curiousity, what do these give you that drawers would not? I use
:todo: and :note: drawers.
For syntax highlighting, I use hi-lock-mode with, for instance, this
patt
i use comments, sometimes with self-highlighted /emphasis/ or
self-highlighted fixme, or demote to a standard "x" task and use tasks
one level above.
if it is exportable, then i use non-task entries as the thing to
export and do not export any tasks. this works pertty well.
on rare occasions i u
I have been exploring the use of something I call editmarks for this
(https://github.com/jkitchin/scimax/blob/master/scimax-editmarks.org).
They are light-weight markups I usually use for commenting org
documents, and they look like this.
{>~ @jk this is a comment~<}
{>*This is a task*<}
with th
On Saturday, 2 Nov 2019 at 14:01, alain.coch...@unistra.fr wrote:
> You also said that you had "already moved to using drawers for a large
> number of [your] inline task use cases, the ones that weren't really
> tasks!". Is this consistent with your "almost completely" above?
> This leads me to t
Fraga, Eric writes on Wed 30 Oct 2019 14:55:
> [...] for a number of reasons including advice from this list, I
> have moved away from inline tasks almost completely and now use
> drawers instead.
As far as I can see, the last discussion about that on the list
occurred in April 2018 (starting
On Friday, 1 Nov 2019 at 23:48, alain.coch...@unistra.fr wrote:
> I have succeeded, following exactly what you suggested. Thank you
> very much.
Excellent. You're very welcome.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78
Fraga, Eric writes on Wed 30 Oct 2019 14:55:
> > By default, the width of LaTeX exported inlinetasks is less than
> > that of regular text.
> >
> > I would like to be able to change this default, ideally both on a
> > per-file basis and a per-inlinetask basis (but either way would
> > alread
On Wednesday, 30 Oct 2019 at 15:21, alain.coch...@unistra.fr wrote:
> Hello.
>
> By default, the width of LaTeX exported inlinetasks is less than that
> of regular text.
>
> I would like to be able to change this default, ideally both on a
> per-file basis and a per-inlinetask basis (but either way
Hello.
By default, the width of LaTeX exported inlinetasks is less than that
of regular text.
I would like to be able to change this default, ideally both on a
per-file basis and a per-inlinetask basis (but either way would
already very good!).
Despite some Internet searching, I could not find
13 matches
Mail list logo
