Am 12.05.2017 um 17:23 schrieb Nicolas Goaziou:
Hello,
Rainer Stengele writes:
I have a wrong clock summary in my agenda and also in clock tables
since 9.0.6. Also the clock sum format suddenly includes days instead
of only hours as before.
I have a function overriding the agenda clocktable
Hello,
Robert Klein writes:
> there are two typos which causes compile to fail. Patch below.
Thank you.
> Options for MathJax (@code{org-html-mathjax-options}). MathJax is
> used to -typeset @LaTeX{} math in HTML documents. @xref{Math
> formatting in HTML -export} for an example.
> +typese
Hi,
there are two typos which causes compile to fail. Patch below.
PS: Probably there should be a comma after the “example”. Sorry, my
English not so good is...
Best regards
Robert
From 355901f48b9b81e9d5509f2df66e4f25eb23adae Mon Sep 17 00:00:00 2001
From: Robert Klein
Date: Mon, 15 May
On Mon, May 15, 2017 at 12:44 AM, John Kitchin wrote:
> This sounds like what TODO keywords are for. For example:
>
> You can easily change the TODO state with shift-left/right on each heading.
>
> #+TODO: TODO CLARIFY | CANCELLED DONE
To make it *look* more similar to your previous workflow, you
The default bibtex key in org-ref is author-year-title, I want to change that
to the Jabref style: AuthorYearJour，just like Steven2016LancetOncol. How to do
that? Thank you!
Nicolas Goaziou writes:
> Kyle Meyer writes:
[...]
>> Using an additional argument whose only purpose is to serve as a
>> interactive flag, which is what called-interactively-p's docstring
>> suggests, avoids these issues.
>
> I'd rather avoid this. What about using
>
> (not (or executing-kb
This sounds like what TODO keywords are for. For example:
You can easily change the TODO state with shift-left/right on each heading.
#+TODO: TODO CLARIFY | CANCELLED DONE
* top-level task
** TODO something I haven't done yet
*** DONE something I've already done
CLOSED: [2017-05-14 Sun 15:12
Hello!
A lot of thanks to all org-mode developers for their work.
I've started using Emacs and org-mode last year, and have been steadily
trying to migrate all of my notes from plain text to org-mode.
I have run into some difficulties with porting over my project notes and
to-do lists. For e
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
-
Thanks for the info, this answers the topic question.
--
Best Regards,
Nikolay Kudryavtsev
Thanks. This removed the need for (org-content).
--
Best Regards,
Nikolay Kudryavtsev
Kyle Meyer writes:
> Won't using a numeric prefix argument change the behavior for both
> interactive and Lisp calls?
>
> As examples,
>
> * M-1 M-x org-sort-list is currently interpreted as a non-nil value
> for WITH-CASE. Instead, it would be indistinguishable from M-x
> org-sort-lis
Nicolas Goaziou writes:
> Kyle Meyer writes:
>
>> I think (interactive "p"), or (interactive "P\np"), would be undesirable
>> because we'd be 1) changing the call signatures in a way that's not
>> backward compatible and 2) positioning an argument that shouldn't
>> concern most users toward the
Is org-save-outline-visibility what you are looking for?
Nikolay Kudryavtsev writes:
> Is there any way to modify node visibility and then revert those
> changes? In particular I'm interested in doing and then reverting
> (org-content).
>
> What follows is more details at what I'm trying to acco
Nicolas Goaziou writes:
> I fixed the issue by extending `org-at-timestamp-p' optional argument
> while preserving backward-compatibility.
Thanks. That seems like a much better soultion than what we've had
before and some of what we've discussed before getting there.
> Is your issue solved?
I'l
Hello,
Achim Gratz writes:
> Yes, put the cursor on the date or time of one of the timestamps and
> press S-Up or S-Down. It should increase or decrease the corresponding
> element of the timestamp, but instead you'll get an error message:
>
> org-clocktable-shift: Line needs a :block definitio
Hello,
Kyle Meyer writes:
> I think (interactive "p"), or (interactive "P\np"), would be undesirable
> because we'd be 1) changing the call signatures in a way that's not
> backward compatible and 2) positioning an argument that shouldn't
> concern most users toward the front of the argument lis
Hello,
Kaushal Modi writes:
[...]
> Well, most of the times, I just report them. The org dev community is very
> active and a reported bug usually gets fixed in a day or two.
yes, that's true. The 'core developers' and all the others, developers
as well as users, do an amazing job and invest a lo
18 matches
Mail list logo
