Brett Viren writes:
> Hi,
Hi Brett,
>> * TODO Subject :emacs_ver:org_ver:org_module:
> ...
>> Emacs version ends up as a tag:
>>
>> * TODO . :24.3:
>
> Or, if I add an Org version:
>
> * TODO . :24.3:8
Hi,
Suvayu Ali writes:
> * TODO Subject :emacs_ver:org_ver:org_module:
...
> Emacs version ends up as a tag:
>
> * TODO . :24.3:
Or, if I add an Org version:
* TODO . :24.3:8.0.3:
These bare numbers
Suvayu Ali writes:
> I forgot to add; regarding your comment about retrieving several
> messages might be expensive, there could be an elisp link or a babel
> source block that does this on demand.
"Elisp link" is the beast I was looking for, thanks. Likely, there is no
need for a babel source b
On Thu, Sep 26, 2013 at 02:13:19PM +0200, Suvayu Ali wrote:
> >
> > Now it comes to the attached emails. In a second (!) step, debbugs-gnu
> > is able to retrieve the corresponding emails. In the given example, it
> > would call (debbugs-get-bug-log 15081) This returns a list like
> >
> > (((body
Hello Michael,
On Thu, Sep 26, 2013 at 11:34:31AM +0200, Michael Albinus wrote:
>
> "Sebastien Vauban"
> writes:
>
> >>> ((source . "unknown")
> >>> (found_versions "24.3")
> >>
> >> Emacs version ends up as a tag:
> >>
> >> * TODO . :24.3:
>
> found_ver
Hi Suvayu,
Suvayu Ali wrote:
> On Thu, Sep 26, 2013 at 09:29:10AM +0200, Sebastien Vauban wrote:
(date . 1376383861)
>>>
>>> * TODO . :24.3:
>>> <2013-08-13 Tue>
>>
>> I'd use the inactive version of the timestamp, that is (for Michael)
>> [2013-08-13
"Sebastien Vauban"
writes:
Hi Sebastien and Suvayu,
Thanks a lot for your comments. That's pretty good for starting a
proof-of-concept. Will do.
Some comments from my side:
>>> ((source . "unknown")
>>> (found_versions "24.3")
>>
>> Emacs version ends up as a tag:
>>
>> * TODO .
On Thu, Sep 26, 2013 at 10:22 AM, Suvayu Ali
wrote:
> On Thu, Sep 26, 2013 at 09:29:10AM +0200, Sebastien Vauban wrote:
>> BTW, is there a convention for using "ALLCAPS" or
>> "First-letter-cap"? I mean: the "time estimate" property is written
>> "Effort", not "EFFORT"; is there a convention to di
Hi Seb and others,
On Thu, Sep 26, 2013 at 09:29:10AM +0200, Sebastien Vauban wrote:
>
> >> (date . 1376383861)
> >
> > * TODO . :24.3:
> > <2013-08-13 Tue>
>
> I'd use the inactive version of the timestamp, that is (for Michael)
> [2013-08-13 Tue].
Doe
Hi Suvayu,
What a nice work you've done... Some comments...
Suvayu Ali wrote:
> This is the general structure I'm proposing:
>
> * TODO Subject :emacs_ver:org_ver:org_module:
> :PROPERTIES:
> :DEBGUGS_ID:
> :REPORTER:
> :CC_EMAIL:
> :END:
>
> I elabora
Hello Michael,
This is the general structure I'm proposing:
* TODO Subject :emacs_ver:org_ver:org_module:
:PROPERTIES:
:DEBGUGS_ID:
:REPORTER:
:CC_EMAIL:
:END:
I elaborate the ideas below.
On Wed, Sep 25, 2013 at 08:56:50PM +0200, Michael Albinus wro
Hi Sébastien,
"Sebastien Vauban"
writes:
> Please note that the "Show Org source" button still shows the old
> Org file.
Indeed -- the sources for all Worg files were not properly updated,
I just fixed this. Thanks!
--
Bastien
"Loyall, David" writes:
>> (I'm not so experienced with org-mode, so I would need at least some
>> assistance how such a TODO item should look like)
>
> A 'headline' is a 'TODO item' if-and-only-if it contains one of the
> TODO Keywords in the appropriate position.
>
> See: http://orgmode.org/wor
On Wed, Sep 25, 2013 at 06:29:26PM +, Loyall, David wrote:
> > (I'm not so experienced with org-mode, so I would need at least some
> > assistance how such a TODO item should look like)
>
> A 'headline' is a 'TODO item' if-and-only-if it contains one of the TODO
> Keywords in the appropriate
Hi Carsten,
Carsten Dominik wrote:
> I have moved the tracker to Worg, discarding the old tracker file that was at
> that location.
>
> http://orgmode.org/worg/org-issues.html
Please note that the "Show Org source" button still shows the old Org file.
Best regards,
Seb
--
Sebastien Vauban
> (I'm not so experienced with org-mode, so I would need at least some
> assistance how such a TODO item should look like)
A 'headline' is a 'TODO item' if-and-only-if it contains one of the TODO
Keywords in the appropriate position.
See: http://orgmode.org/worg/dev/org-syntax.html
While you're
Hi Michael,
Michael Albinus wrote:
> "Sebastien Vauban"
>
The other solution that I'd see would be using Emacs' own bug tracker (the
`org' package is already known to them), if that's
possible. Anyway, having the
bugs in an Org file seems natural too!
>>>
>>> I think this is a
"Sebastien Vauban"
writes:
> Hi Suvayu,
Hi,
>>> The other solution that I'd see would be using Emacs' own bug tracker (the
>>> `org' package is already known to them), if that's
>>> possible. Anyway, having the
>>> bugs in an Org file seems natural too!
>>
>> I think this is a great idea. A
Hi Sebastiaan,
I have added your issues.
(P.S. this sounds really funny and reminds me of Marvin from the
"Hitchhikers Guide to the Galaxy" does solve "all of the
major mathematical, physical, chemical, biological, sociological,
philosophical, etymological,meteorological and psychological
problem
Hi Suvayu,
Suvayu Ali wrote:
> On Wed, Sep 25, 2013 at 09:51:20AM +0200, Sebastien Vauban wrote:
>>
>> The other solution that I'd see would be using Emacs' own bug tracker (the
>> `org' package is already known to them), if that's possible. Anyway, having
>> the
>> bugs in an Org file seems nat
Carsten Dominik wrote:
> On 25.9.2013, at 09:51, Sebastien Vauban wrote:
>> Carsten Dominik wrote:
>>> we do not have an issue tracker for Org. However, if you
>>> have some time to help, the file with open issues that need
>>> attention can be found here:
>>>
>>> https://dl.dropboxusercontent.c
On 25.9.2013, at 08:43, Carsten Dominik wrote:
> Hi everyone,
>
> we do not have an issue tracker for Org. However, if you
> have some time to help, the file with open issues that need
> attention can be found here:
>
> https://dl.dropboxusercontent.com/u/530458/org-tracker.html
I have moved
On Wed, Sep 25, 2013 at 09:51:20AM +0200, Sebastien Vauban wrote:
>
> The other solution that I'd see would be using Emacs' own bug tracker (the
> `org' package is already known to them), if that's possible. Anyway, having
> the
> bugs in an Org file seems natural too!
I think this is a great id
On 25.9.2013, at 09:51, Sebastien Vauban wrote:
> Hi Carsten,
>
> Carsten Dominik wrote:
>> we do not have an issue tracker for Org. However, if you
>> have some time to help, the file with open issues that need
>> attention can be found here:
>>
>> https://dl.dropboxusercontent.com/u/530458/
Hi Carsten,
Carsten Dominik wrote:
> we do not have an issue tracker for Org. However, if you
> have some time to help, the file with open issues that need
> attention can be found here:
>
> https://dl.dropboxusercontent.com/u/530458/org-tracker.html
>
> Note that I do not enter every issue into
On 25.9.2013, at 09:28, Christian Moe wrote:
>
> Hi,
>
> I was going to ask about this.
>
> The website actually does direct people to a collaborative issue tracker
> on Worg:
>
> http://orgmode.org/worg/org-issues.html
Ha, I completely forgot about this one, and it seems
to be entirely out
Hi,
I was going to ask about this.
The website actually does direct people to a collaborative issue tracker
on Worg:
http://orgmode.org/worg/org-issues.html
As outlined there, the idea was that the maintainer would add issues
from the mailing list, but others were welcome to modify the entries
Hi everyone,
we do not have an issue tracker for Org. However, if you
have some time to help, the file with open issues that need
attention can be found here:
https://dl.dropboxusercontent.com/u/530458/org-tracker.html
Note that I do not enter every issue into this file. Normally I wait
and se
28 matches
Mail list logo
