Re: Switching to new Git repositories

f it's because there's something else planned for the tags, or if this was just an oversight. Éibhear > > I wonder if it's related to a problem I have on one of the two machines > (both Ubuntu, with identical setups) where I run Org from source. > > On one, when

Re: Switching to new Git repositories

gs missed in the migration across to savannah? Thanks, Éibhear =8<- $ git -C org-mode.orig remote -v origin https://code.orgmode.org/bzg/org-mode.git (fetch) origin https://code.orgmode.org/bzg/org-mode.git (push) $ git -C org-mode.orig tag | wc -

Re: Editting from the agenda view

Hi, Have a look at the agenda columns view in the documentation. I find it very useful for editing items in situ in the agenda. Éibhear > Dear all, > > Apologies for what's probably a totally dumb question but I am unable to > find the answer although I did read the doc. &g

[O] Bug: Clock report failing with "invalid time specification" [9.2.1 (9.2.1-dist @ /home/eibhear/eibhear_org/lisp/org-9/lisp/)]

ktable :scope file :maxlevel 2 :block thisweek :step week #+END: Typing C-c C-c to refresh the table results in an error "invalid time specification", failing on line 2738 of org-clock.el. When I revert to org-9.2.0, the error is present, but when I revert to org-9.1.9, the clocktable refr

[O] Bug: org-agenda-columns failing when Diary entries are included [9.0.5 (9.0.5-dist @ /home/ohanluaine/eibhear_org/lisp/org-9/lisp/)]

In the same org-agenda-list view, jump to 2017-04-16. This has two entries, "Easter Sunday" as a calculated diary entry and "Eat your chocolate egg" from the org-mode file. Calling org-agenda-columns succeeds. Discussion == The error occurs in org-colu

Re: [O] [PATCH] Prevent overwriting of output files from babel calls with nil result

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/10/15 19:59, Aaron Ecay wrote: > Hi Éibhear, > > Thanks for sending the example. I think it is not expected to > work going forward because the lisp block relies on being able to > pick up the value of ‘params’, which will not

Re: [O] [PATCH] Prevent overwriting of output files from babel calls with nil result

> Hi Éibhear, > > I'm afraid I don't understand the problem the patch is trying to fix. > Can you provide a MWE (minimal working example) that illustrates the bug > you're observing? > > Thanks, > > -- > Aaron Ecay > Hi Aaron, Thanks for getti

[O] [PATCH] Prevent overwriting of output files from babel calls with nil result

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Here's a patch to ob-emacs-lisp.el to allow me to start generating graphs with dot again. Thanks, Éibhear - -- Éibhear Ó hAnluain Dublin, Ireland. +---++ | e-mail: ei

Re: [O] org-babel-execute:dot -- why doesn't this work?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/10/15 18:43, Matt Price wrote: > > > On Fri, Oct 23, 2015 at 8:27 AM, Éibhear <mailto:eibhear@gmail.com>> wrote: > > Matt Price gmail.com <http://gmail.com>> writes: > >> >> &g

Re: [O] org-babel-execute:dot -- why doesn't this work?

9DTL/dot-2749Nkt -Tpng -o /home/matt/example-diagram.png"  "")  > > from a scratch buffer also works.  So I am really confused -- maybe there is something wrong with ob-dot itself? > > > > > Again, many thanks, > > Matt > > > > > > > Hi Matt, Did you get this worked out? Thanks, Éibhear