Daniel Bausch writes:
>> > However, I'd like to ask, what happens, if one refers to a
>> > name of a source block where data is expected, does it then refer to
>> > the results produced by that source block? How are such situations
>> > handeled at the moment?
>>
>> Try it out, but be ready to
Hi. Clocking capability is nice and powerful.
I'm wondering if there is a way to generate a clocking table for ALL org
files that are registered as "org-agenda-files" ?
I have currently set up several agenda files in order to keep track of many
projects. I use the clocking functionality for each
Am Dienstag 25 Oktober 2011, 19:21:22 schrieb Nick Dokos:
> Eric Schulte wrote:
> > Martyn Jago writes:
> > > Nick Dokos writes:
> > >> Eric Schulte wrote:
> > >>> Surprisingly (to me) srcname is the winner here, but luckily I
> > >>> haven't yet voted, and although I would have though #+source
Hi Frozenlock,
Frozenlock writes:
> I'm trying to push my changes to the Worg repo, but it asks me for my
> repo.or.cz's password.
> This confuses me, as the repo.or.cz states that they don't use
> password.
You need to register as a user on repo.or.cz:
http://repo.or.cz/reguser.cgi
then wr
> > However, I'd like to ask, what happens, if one refers to a
> > name of a source block where data is expected, does it then refer to
> > the results produced by that source block? How are such situations
> > handeled at the moment?
>
> Try it out, but be ready to press C-g, because I would gue
Hi Bastien,
I'm trying to push my changes to the Worg repo, but it asks me for my
repo.or.cz's password.
This confuses me, as the repo.or.cz states that they don't use password.
One of the changes I've made is to host the org-bom.el on github
(better than pastebin).
https://github.com/Frozenlock/
Hi,
The tags search for org-sparse-tree seems to be broken. With a minimal
setup, C-c / m RET doesn't perform a tags search. I bisected
the problem to this commit.
dfcb6faef11a2439b56b18a6289803361d402130 is the first bad commit
commit dfcb6faef11a2439b56b18a6289803361d402130
Author: Nicolas Go
Hi list, with help and substancial input from Eric (Schulte) I added a
new language to org-babel, the minimal lisp dialect picolisp [thanks to
Eric!]. You can download the ob-picolisp.el file here:
https://github.com/tj64/ob-picolisp
Here is the README text as a little introduction to picolisp:
I am an emacs novice attempting to use an org-capture template. The
manual indicates completion is available while expanding %^{prompt}.
Can one get completion on %^{prop}p for a property? I tried the same
syntax for prompt and that did not work.
David
Ha, the XMPP idea really appeals to me, endless possibilities :D
Thanks for sharing.
On Mon, Oct 24, 2011 at 10:01 AM, Christopher Allan Webber <
cweb...@dustycloud.org> wrote:
> Hey Peter,
>
> I also do appointments with orgmode.. I have it hooked up so that it
> sends me messages via XMPP/Jab
Hi
Brian Wightman writes:
> On Mon, Oct 24, 2011 at 7:12 AM, Sebastien Vauban
> wrote:
>> For my information, why do you need to test that 2 suites don't run at the
>> same time? They only write to temp buffers, no? Can they conflict?
>
> If they do conflict and only one set of tests should r
Eric Schulte wrote:
> Martyn Jago writes:
>
> > Nick Dokos writes:
> >
> >> Eric Schulte wrote:
> >>
> >>> Surprisingly (to me) srcname is the winner here, but luckily I haven't
> >>> yet voted, and although I would have though #+source: would have been
> >>> the winner I like the simplicity
Hi Carsten,
On Tue, 25 Oct 2011 16:08:43 +0200, Carsten Dominik
wrote:
>
> The first is accepted. The second I have modified. If any of
> SKIP-WEEKS is the symbol `holidays', then holidays will be skipped.
That sounds good.
Thank you.
Regards,
Rüdiger
On 24 October 2011 08:00, Bastien wrote:
> Hi Brian,
>
> suvayu ali writes:
>
>> Ah I see it now, you want the org-timestamp command to work on a
>> region. Maybe you can write your own function with lisp if you are
>> doing this too often. Should be quite simple to try.
>
> Please check `org-loo
Martyn Jago writes:
> Nick Dokos writes:
>
>> Eric Schulte wrote:
>>
>>> Surprisingly (to me) srcname is the winner here, but luckily I haven't
>>> yet voted, and although I would have though #+source: would have been
>>> the winner I like the simplicity of using #+name: for named code blocks
>
Nick Dokos writes:
> Eric Schulte wrote:
>
>> Surprisingly (to me) srcname is the winner here, but luckily I haven't
>> yet voted, and although I would have though #+source: would have been
>> the winner I like the simplicity of using #+name: for named code blocks
>> as well as named data. So I
>
> Then maybe #+results for (anonymous) results only, but #+name for anything
> else from [1] and [3].
This seems like a reasonable approach.
> Wasn't there a concept of linking a results block to its originiating
> source block by some id and we need a place to put the checksum in.
Not that I
> I think that makes sense.
>
> While thinking about all of this, and working in real-life documents, I just
> came back to a suggestion which I made some time ago. It goes about this
> enhancement:
>
> Would it be possible to specify "buffer-wide language specific" header
> arguments?
>
Y
Nicolas Goaziou writes:
>> I found two errors of org while handling asterisks "*" in HTML export.
>> I don't think this is a bug, but I think it is worth to report.
>
> I've pushed a fix in master. Could you confirm that it is working?
>
yes it works,
thanks,
Giovanni
Eric Schulte wrote:
> Surprisingly (to me) srcname is the winner here, but luckily I haven't
> yet voted, and although I would have though #+source: would have been
> the winner I like the simplicity of using #+name: for named code blocks
> as well as named data. So I'll vote for #+name: here ma
Surprisingly (to me) srcname is the winner here, but luckily I haven't
yet voted, and although I would have though #+source: would have been
the winner I like the simplicity of using #+name: for named code blocks
as well as named data.
Ditto -- it just wasn't on the table yet when I cast my vo
Am 25.10.2011 16:42, schrieb Nicolas Goaziou:
> Hello,
>
> Giovanni Ridolfi writes:
>
>> I found two errors of org while handling asterisks "*" in HTML export.
>> I don't think this is a bug, but I think it is worth to report.
>
> I've pushed a fix in master. Could you confirm that it is workin
Alright,
I've tallied up the results and we have the following (with full voting
information below [1]).
Call lines
| call | 13 |
It seems unanimous that remote code block calls should use the #+call:
syntax moving forward.
Data and result names
| (name results) | 3 |
| name | 2 |
Hello,
Giovanni Ridolfi writes:
> I found two errors of org while handling asterisks "*" in HTML export.
> I don't think this is a bug, but I think it is worth to report.
I've pushed a fix in master. Could you confirm that it is working?
Please note that single stars, in part 1 and 3, won't ap
I have the same problem
this org file creates the bug:
* headline
* test
this doesn't:
* headline
- test
Best,
Rainer
Am 25.10.2011 15:21, schrieb Giovanni Ridolfi:
>
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know h
Hi Rüdiger,
On Oct 10, 2011, at 9:15 PM, Rüdiger Sonderfeld wrote:
> Hello,
> I wrote two small patches. The first one marks org-diary-class as obsolete
> (according to its documentation it is deprecated). The second one is a
> patch for org-class. It changes org-class to skip entries that are on
Nick Dokos writes:
> zwz wrote:
>
>
>> >> Then you modify it:
>> >> #+begin_src org
>> >> * test
>> >> #+BEGIN_SRC c
>> >> void main(){
>> >> int a[5];
>> >> }
>> >> #+END_SRC
>> >> #+end
>> >>
>> >> It says "org-export-latex-preprocess: Wrong type argument: stringp,
>> > nil"
>> >>
Just bumping this in case anyone can help me fix it - I'd really like
the tasks to be greyed out in an export.
Thanks,
Gez
On 13 October 2011 12:57, Gez wrote:
> I use org-agenda-dim-blocked-tasks to keep track of "tasks" that have
> no current "todo's", but in my exported html agenda view (C-c
Hi!
I want to share a solution that allows lbdb[1] queries return
Org-contacts[2] email addresses. The solution is done by Russell
Adams who encouraged me to post it here because he did only mention
it in [3] but did not post the results yet. I took Russells solution
and modified it to be of more
On Mon, Oct 24, 2011 at 7:12 AM, Sebastien Vauban
wrote:
> For my information, why do you need to test that 2 suites don't run at the
> same time? They only write to temp buffers, no? Can they conflict?
If they do conflict and only one set of tests should run at a time,
shouldn't the second set
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.
-
Hi,
I set up org todo keyword faces like so:
(setq org-todo-keyword-faces
'(("FAIL" . org-warning)
("MISSING" . org-warning)
))
But at html export, the keywords are green because they are done
states. So additionally I have to set :
(setq org-export-html-style-extra
"
Hi!
See the attached org-file for more information. Hitting return on a link
in a description list does not follow the link but insert .
I have org-return-follows-link set to t.
Regards, Max
link.org
Description: Binary data
Hello,
there is a bug when exporting to LaTeX if there is a source code block
inside a list.
I have a file with the following contents:
#+begin_org
#+TITLE: Lists mit Source-Blocks
#+AUTHOR:thomas.ho...@gmx.de
#+EMAIL: Thomas Holst
#+DATE: 25.10.2011
#+LANGUAGE: en
On Tue, Oct 25, 2011 at 12:31 PM, Sebastien Vauban <
wxhgmqzgw...@spammotel.com> wrote:
> Hi Rainer,
>
> Rainer M Krug wrote:
> >> While thinking about all of this, and working in real-life documents, I
> >> just
> >> came back to a suggestion which I made some time ago. It goes about this
> >> en
"Sebastien Vauban"
writes:
>> And
>>
>> (setq system-time-locale (getenv "LANG"))
>>
>> resulting in "en_US.utf8" seems to work as well. What did not work
>> for you in the agenda?
>
> When I wrote (months ago) "did not work", I meant: I got French
> weekdays in my agenda ("Lun." for Monday, "
Hi Tassilo,
Tassilo Horn wrote:
> "Sebastien Vauban" writes:
>
>>> What's going on? I even have no glue how org/emacs (correctly)
>>> guesses that I'm German. My locale is en_US.UTF-8...
>>
>> Found in my .emacs:
>>
>> #+begin_src emacs-lisp
>> ;; system locale to use for formatting time
Hi Rainer,
Rainer M Krug wrote:
>> While thinking about all of this, and working in real-life documents, I
>> just
>> came back to a suggestion which I made some time ago. It goes about this
>> enhancement:
>>
>>Would it be possible to specify "buffer-wide language specific" header
>>argum
"Sebastien Vauban"
writes:
Hi Sebastien,
>> What's going on? I even have no glue how org/emacs (correctly)
>> guesses that I'm German. My locale is en_US.UTF-8...
>
> Found in my .emacs:
>
> #+begin_src emacs-lisp
> ;; system locale to use for formatting time values (e.g., timestamps in
On Tue, Oct 25, 2011 at 11:35 AM, Sebastien Vauban <
wxhgmqzgw...@spammotel.com> wrote:
> Hi Eric,
>
> Eric Schulte wrote:
> >> #+BABEL: :var SVNVERSION=(vc-working-revision (buffer-file-name))
> >> #+BABEL: :var SVNSTATE=( symbol-name (vc-state (or (buffer-file-name)
> org-current-export-file)))
"Sebastien Vauban" writes:
> Hi Tassilo,
>
> Tassilo Horn wrote:
>> when I insert a new timestame, I now get
>>
>> <2011-10-25 Di>
>>
>> while it used to be <2011-10-25 Tue> until very recently. (Di is
>> Dienstag which is German for Tuesday). I've briefly grepped the org
>> source code, but
Hi Tassilo,
Tassilo Horn wrote:
> when I insert a new timestame, I now get
>
> <2011-10-25 Di>
>
> while it used to be <2011-10-25 Tue> until very recently. (Di is
> Dienstag which is German for Tuesday). I've briefly grepped the org
> source code, but I cannot see any localization there.
>
>
Hi all,
when I insert a new timestame, I now get
<2011-10-25 Di>
while it used to be <2011-10-25 Tue> until very recently. (Di is
Dienstag which is German for Tuesday). I've briefly grepped the org
source code, but I cannot see any localization there.
What's going on? I even have no glue h
Hi Eric,
Eric Schulte wrote:
>> #+BABEL: :var SVNVERSION=(vc-working-revision (buffer-file-name))
>> #+BABEL: :var SVNSTATE=( symbol-name (vc-state (or (buffer-file-name)
>> org-current-export-file)))
>> #+BABEL: :var SVNSTATENUM=(if (eq (vc-state (or (buffer-file-name)
>> org-current-export-fil
Hi Rainer,
Rainer M Krug wrote:
> On Fri, Oct 21, 2011 at 6:24 PM, Eric Schulte wrote:
>>> Just to make it as easy as possible for everyone
>>> Might it be possible to introduce a small flags like "obsolete" and
>>> "stable" (standard)
>>> Old functions, old syntax, etc., might move first to o
Hi Daniel,
Daniel Bausch wrote:
> Am Dienstag 25 Oktober 2011, 03:30:46 schrieb Eric Schulte:
>> "Sebastien Vauban" writes:
>> > Daniel Bausch wrote:
>> >>> named code blocks [1] -- "source" "srcname" "function"
>
> calling external functions [2] -- "call" "lob"
>
>
> #+object_begin var
> x = 1
> y = 2
> #+end
I was thinking on similar lines. This together with Nicolas's suggestion
of "one name" will be wonderful.
I think it is easier to explain what I think by means of an example. In
case of lisp, the SAME variable name could either act as a function or a
Am Dienstag 25 Oktober 2011, 03:30:46 schrieb Eric Schulte:
> "Sebastien Vauban" writes:
> > Hi Daniel,
> >
> > Daniel Bausch wrote:
> >>> named code blocks [1] -- "source" "srcname" "function"
> >>>
> >>> calling external functions [2] -- "call" "lob"
> >>>
> >>> named
48 matches
Mail list logo
