Hello,
Tim Landscheidt writes:
> I wanted to (and did) change a number of timestamps by a
> constant. So I found (and successfully used)
> org-timestamp-change which starts with (master):
>
> | […]
> | (defun org-timestamp-change (n what updown suppress-tmp-delay)
> | "Change the date in
On Monday, 6 May 2019 at 14:17, Matt Price wrote:
> So, I'm finding more and more that I want to include simple diagrams in my
> course materials. At present I am generating them as svg's using Inkscape,
> but that feels really tiresome to me. I would much rather make them
> programmatically,
Dear Martin,
Just go to the beginning of buffer and (while (re-search-forward
org-clock-line-re) (org-ctrl-c-ctrl-c)) . Or you can use keyboard
macros ;)
Best,
Ihor
Martin Schroeder writes:
> I have imported a bunch of log lines with CLOCK periods from another
> program into an org file but
Hi,
FYI: the documentation still talks about org-mark-entry-for-agenda-action even
though this function
was removed in f95e5ff.
Best regards
Christian
Hi,
Am 07.05.19 um 11:07 schrieb Martin Schroeder:
> I noticed that on timestamps that begin or end at 00:00 the org mode
> org-evaluate-time-range function seems to produce wrong results. Here
> are some examples:
>
> For example, this should produce 2:00 duration:
> CLOCK: [2019-04-19 Fri
I noticed that on timestamps that begin or end at 00:00 the org mode
org-evaluate-time-range function seems to produce wrong results. Here
are some examples:
For example, this should produce 2:00 duration:
CLOCK: [2019-04-19 Fri 22:00]--[2019-04-19 Fri 00:00] => -22:00
I tried this, but id did
I have imported a bunch of log lines with CLOCK periods from another
program into an org file but I have forgotten to calculate periods. So
my time lines look like this:
CLOCK: [2019-03-27 Wed 19:30]--[2019-03-27 Wed 21:30]
Instead of this:
CLOCK: [2019-03-27 Wed 19:30]--[2019-03-27 Wed 21:30]
Duration must not endure for more than 24 hours since that's
unendoreable.
On Tue, 7 May 2019, Martin Schroeder wrote:
> Date: Tue, 7 May 2019 05:07:58
> From: Martin Schroeder
> To: emacs-orgmode@gnu.org
> Subject: [O] Incorrect clock duration calculation
>
> I noticed that on timestamps that
Hi Ihor
On Tue, May 7, 2019 at 5:27 AM Ihor Radchenko wrote:
> I am wondering why you are strictly against ID properties.
To me this looks like a misunderstanding. I use the ID often but my
weighting of the different advantages is not the same in all cases.
Some situations where no ID can be
Thanks, everything's fine now. Sorry for late reply.
Icicles is doing it wrong. Packages are supposed to provide only
prefixed functions, since there is no namespace in Emacs.
As far as I could grasp, those are shorthand alias functions created for
easier access. Luckily that behavior can be
On Tuesday, 7 May 2019 at 13:22, Matt Price wrote:
> I thought that a latex src block with :exports results would work, but
> rather than a rendered graph I end up with a .png of the latex
> instructions themselves. Here's what I am trying:
It should work. Try with the following header
Yeah I ended up using a macro and search for CLOCK text but this
solution is much cleaner
On Tue, May 7, 2019 at 6:04 PM Ihor Radchenko wrote:
>
> Dear Martin,
>
> Just go to the beginning of buffer and (while (re-search-forward
> org-clock-line-re) (org-ctrl-c-ctrl-c)) . Or you can use
Note that the day starts at 00:00 and ends at 24:00. So:
Martin Schroeder wrote at 11:07 on May 7, 2019:
: For example, this should produce 2:00 duration:
: CLOCK: [2019-04-19 Fri 22:00]--[2019-04-19 Fri 00:00] => -22:00
It will if you change [2019-04-19 Fri 00:00] to [2019-04-19 Fri 24:00].
:
These are all great. I am struggling to some extent through the docs for
all these tools. Eric, for the most part I'm very happy with graphviz &
plantufml but I would be interested in trying latex as well. Since I'm
mostly exporting to html and its derivatives (markdown mostly), I don't
think
hmm, I still get just the attached image (approx). Presumably osmehting
wrong w/ my latex setup (I use latex only very rarely).
On Tue, May 7, 2019 at 1:52 PM Fraga, Eric wrote:
> On Tuesday, 7 May 2019 at 13:22, Matt Price wrote:
> > I thought that a latex src block with :exports results
Maybe missing a "\usepackage{tikz}"?
(That caught me out)
--
Martin Schöön
On 2019-05-06, at 20:17, Matt Price wrote:
> So, I'm finding more and more that I want to include simple diagrams in my
> course materials. At present I am generating them as svg's using Inkscape,
> but that feels really tiresome to me. I would much rather make them
> programmatically,
On Tuesday, 7 May 2019 at 22:51, Martin Schöön wrote:
> Maybe missing a "\usepackage{tikz}"?
> (That caught me out)
Ah, that is a very likely reason! I have the following in my emacs
initialization for org:
(add-to-list 'org-latex-packages-alist '("" "tikz"))
(add-to-list
18 matches
Mail list logo
