Is there a way to specify the timestamp for a repeated task which has to
be done on the second Sunday of every month? I'd like the todo state of
the task to go back to TODO after it has been marked DONE, as described
in the section on repeated tasks in the Org manual.
Thanks,
Raghu.
PS: I am sor
Hi Nicolas,
2016ko maiatzak 11an, Nicolas Goaziou-ek idatzi zuen:
> I changed this in developement version. If you get any chance to test
> it, Please tell me if it behaves as expected. Thank you.
Is this a correct change? Previously, C-x C-s in the org-src buffer
would save the underlying .org
Hi Rasmus, hi all,
2016ko maiatzak 8an, Rasmus-ek idatzi zuen:
[...]
> As you mention, we’d loose the ability to chain together multiple blocks.
> I reckon they are meaningfully the same language, so I don’t see a loss.
> The example shown in the manual also does not convince me of the
> usefull
OK, so I have an issue with capture and completion. On the following
template:
#+BEGIN_SRC org
* %^{Subject?}
:PROPERTIES:
:CREATED: %T
:END:
%?
#+END_SRC
When I go to capture, and I enter my value for the ~%^{Subject?}~
prompt, as soon as I hit "space", I get an window pop-up about "No
Complet
Okay, I have deleted the org one and left the org-contrib:
I can still use the new feature (probably org-contrib enables it).
Thanks for your explanation,
Andrea
Kaushal Modi writes:
> On Thu, May 12, 2016 at 6:20 PM Andrea wrote:
>
>> I think I saw that, but I did not read it carefully. And s
On Thu, May 12, 2016 at 6:20 PM Andrea wrote:
> I think I saw that, but I did not read it carefully. And since the
> autocompletion (I mean not occur to me that may be the problem.
>
> By the way, I did not clone the git repo, so I should be on the master
> published on ELPA.
The versions publ
I think I saw that, but I did not read it carefully. And since the
autocompletion (I mean writes:
>
> But I am surprised that that fix applied to your org-plus-contrib version.
>
> It applies only to the version built from the master branch. Is
> org-plus-contrib the only version that you have in
On Thu, May 12, 2016 at 5:38 PM Andrea wrote:
> Hello,
>
> thanks for the fast reply. It actually works with the new syntax, thank
> you!
> There is a minor thing though: when I export a #+BEGIN_export latex to
> an org buffer, it exports to #+BEGIN_export (without the latex). Maybe
> this is a b
Hello,
thanks for the fast reply. It actually works with the new syntax, thank
you!
There is a minor thing though: when I export a #+BEGIN_export latex to
an org buffer, it exports to #+BEGIN_export (without the latex). Maybe
this is a bug?
Thanks,
Andrea
P.S: I did not know about these changes,
John Hendy writes:
> There's no worg page for the shell language (surprised me!).
Several babel languages in core lack documentation on Worg in addition
to shell: calc, comint, coq, ebnf, emacs-lisp(!), forth, fortran,
haskell, io, java, javascript, objective caml, org(!!!), perl, plantuml,
proc
This is a known issue with diff, I think. Add a line containing ":" below, or
"echo" or "diff foo bar | cat".
https://stackoverflow.com/questions/27304469/capturing-the-output-of-diff-with-org-babel
I have
(setq org-babel-default-header-args:sh
'((:prologue . "exec 2>&1") (:epilogue . ":"))
On Thu, May 12, 2016 at 2:24 PM, Kaushal Modi wrote:
>
> On Thu, May 12, 2016 at 3:16 PM John Hendy wrote:
>>
>> Ah. I always wondered about that since the change is reported for 9.0
>> but it's in effect for me on:
>>
>> Org-mode version 8.3.4 (release_8.3.4-753-gda4db33 @ ~/.elisp/org/lisp/)
>>
Hello,
I've not used shell in babel much, and am confused. I was trying to
include diff output from a block in an analysis and it's not giving
any output.
As a test, I have a.txt which contains 1 and b.txt which contains 2,
with boths in ~/Desktop.
Manually:
$ cd ~/Desktop
$ diff a.txt b.txt
1c
Ah. I always wondered about that since the change is reported for 9.0
but it's in effect for me on:
Org-mode version 8.3.4 (release_8.3.4-753-gda4db33 @ ~/.elisp/org/lisp/)
But I've obviously built from git. Simple case would be for Andrea to
just try it and let us know :) Other than that, I'd de
On Thu, May 12, 2016 at 2:53 PM John Hendy wrote:
> I believe this is due to the new syntax change for export blocks
> announced a bit back. See:
> - http://orgmode.org/cgit.cgi/org-mode.git/plain/etc/ORG-NEWS
>
> Try this instead:
>
> * Hello
> #+BEGIN_export latex
> hi I am latex
> #+END_export
On Thu, May 12, 2016 at 11:57 AM, Andrea wrote:
>
> 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
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-mode mailing list.
-
I'm trying to dip my toes into the waters of customizing org-mode somewhat,
so I'm unsure as to where to look.
Is there an easy way to return the text of the parent header? In other
words, if I had this in the agenda prefix, and the agenda file read:
* One
** TODO Two
It would show in the agenda
Forgot to mention my emacs and org versions; here they are:
GNU Emacs 25.0.93.5 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.23) of
2016-05-05
Org-mode version 8.3.4 (release_8.3.4-778-g8127b3 @
/home/kmodi/usr_local/apps/6/emacs/emacs-25/share/emacs/site-lisp/org/)
--
--
Kaushal Modi
Hi all,
I almost have a squeaky clean solution to this thanks to the hint provided
by someone on emacs.SE ( http://emacs.stackexchange.com/a/22215/115 ).
But in the process, I seem to have stumbled upon a bug.. the buffer local
value of variables are not respected at the time of exports.
To demo
Hello,
Julien Cubizolles writes:
> I'm still experiencing this problem with the following example
>
> #+BEGIN_SRC elisp
> (add-to-list 'load-path "~/git-repositories/org-mode/lisp")
> (add-to-list 'load-path "~/git-repositories/org-mode/contrib/lisp")
> #+END_SRC
>
> #+RESULTS:
> : Successfu
Nicolas Goaziou writes:
> Would the following patch solve the issue?
I'm still experiencing this problem with the following example
--8<---cut here---start->8---
#+BEGIN_SRC elisp
(add-to-list 'load-path "~/git-repositories/org-mode/lisp")
(add-to-list '
22 matches
Mail list logo