Re: issue tracker?

Bastien writes: > I have setup this page on orgmode.org which now tracks confirmed bugs: > > https://updates.orgmode.org I've updated https://updates.orgmode.org The main change is that Woof! now tracks help requests separately. You can publish a help request on the list by adding this

Re: issue tracker?

Hi Mario, > On 07/06/2020 04:38, Bastien wrote: > > anybody can > 'vote-for' a bug, and you keep a counter on voted-for. > > It would require people to register on updates.orgmode.org. > I'm not sure the expected benefit is really worth it for now. > > why

Re: issue tracker?

good day Bastien On 07/06/2020 04:38, Bastien wrote: anybody can 'vote-for' a bug, and you keep a counter on voted-for. It would require people to register on updates.orgmode.org. I'm not sure the expected benefit is really worth it for now. why would it?  you already trust email senders on

Re: issue tracker?

Hi Mario, Mario Frasca writes: > very interesting approach.  Thanks for looking more closely into it. > sounds like you don't want to manage the status changes a bit > tighter.  I know, I can check the code, but it's more practical if we > mention it here explicitly.  anybody can send status

Re: issue tracker?

: Hi Mario, Beware that this is not meant to be an issue tracker. I understand, not a bug "tracking" tool, but it sounds like it's able to shed some light in the dark. thank you and cheers, Mario

Re: issue tracker?

Hi Mario, Mario Frasca writes: > I sent the pdf for contributing, and I have a question on how to use > this email-based issue tracker: Beware that this is not meant to be an issue tracker. > how do I get the list of open issues?  complete with the status > accepted/wont-fix/whate

Re: issue tracker?

you as a committer. I sent the pdf for contributing, and I have a question on how to use this email-based issue tracker: how do I get the list of open issues?  complete with the status accepted/wont-fix/whatever? best regards

Re: issue tracker?

Hi Mario, Mario Frasca writes: > On 01/06/2020 10:53, Bastien wrote: >> Let us know what would help you contribute more. > > as mentioned, I would like to correct docstrings, refactor the code in > a few points, and add unit tests. Please go ahead. Read

Re: issue tracker?

Hi Vladimir, Vladimir Nikishkin writes: > Does any other email client apart from Gnus support adding > additional headers? M-x mail RET M-x compose-mail RET And surely quite a few other email clients, even outside Emacs. If a user cannot set the headers herself, that's not a problem: someone

Re: issue tracker?

Does any other email client apart from Gnus support adding additional headers? -- Yours sincerely, Vladimir Nikishkin

Re: issue tracker?

On Mon, Jun 01, 2020 at 11:28:48AM -0500, Mario Frasca wrote: > On 01/06/2020 10:53, Bastien wrote: > > Let us know what would help you contribute more. > > as mentioned, I would like to correct docstrings, refactor the code in a > few points, and add unit tests. > > I've not been collecting them,

Re: issue tracker?

On 01/06/2020 10:53, Bastien wrote: Let us know what would help you contribute more. as mentioned, I would like to correct docstrings, refactor the code in a few points, and add unit tests. --- (defun org-plot/gnuplot-script (data-file num-cols params preface)   "Write a gnuplot script to

Re: issue tracker?

Hi Mario, Mario Frasca writes: > while working on my contribution, I'm also reading the code I'm adding > to, and I am tempted to perform unrelated edits, like correcting a > docstring to a function that does something, just not quite what the > docstring says, or refactoring stuff in order to

Re: issue tracker?

Hi Bastien, in the meanwhile someone found the patch, and we are working on it. thank you for the feedback! but it stays confusing, and sure I get the point, people here are volunteers, working on their free time, but precisely for this reason it would be better if we could rely on some more

Re: issue tracker?

Hi Anthony, Anthony Carrico writes: > Does org-mode have an issue tracker, to keep track of which issues > are active, or is it just this mailing list? thanks for asking. I've skimmed through https://orgmode.org/worg/org-faq.html and the question "Does org-mode have an is

Re: issue tracker?

Hi Mario, Mario Frasca writes: > myself, I recently posted a patch, received zero reaction, and have > the impression it's now lost in the logs of this mailing list.  indeed > pretty inefficient! Sorry for that. As others have mentioned, Org developers are working on their free time to

Re: issue tracker?

I also wholeheartedly agree with Matt and Detlef: I find emails to be the best way to deal with bug reports. Matthew Lundin writes: > I agree wholeheartedly with everything Detlef says here. Due to life > circumstances, I have only been able to participate intermittently on > the mailing list

Re: issue tracker?

Hi Roland, Roland Everaert writes: > [QUESTION] -> [ANSWER] > [BUG] -> ( [CONFIRMED] | [WONTFIX] | [SOLVED] ) > [CONFIRMED] -> ( [SOLVED] | [PLANNED] ) > [FEATURE] -> ( [WONTDO] | [PLANNED] | [IMPLEMENTED] ) > [PLANNED] -> ( [IMPLEMENTED] | [SOLVED] ) as others in this thread, I'm skeptical

Re: issue tracker?

Hi Eric, Eric Abrahamsen writes: > Maybe a first step would be changing `org-submit-bug-report' to submit > the bug to debbugs, not to this mailing list? I'd like to keep this mailing list as the central place to discuss everything about Org, including bug reports. When Org bugs are reported

Re: issue tracker?

On Wed, May 27, 2020 at 12:59:24PM -0500, Mario Frasca wrote: > myself, I recently posted a patch, received zero reaction, and have the > impression it's now lost in the logs of this mailing list.  indeed > pretty inefficient! Have to point out, that you received replies after about a week.

Re: issue tracker?

Russell Adams writes: > On Wed, May 27, 2020 at 12:59:24PM -0500, Mario Frasca wrote: >> myself, I recently posted a patch, received zero reaction, and have the >> impression it's now lost in the logs of this mailing list.  indeed >> pretty inefficient! > > Or the devs haven't had a chance yet.

Re: issue tracker?

On Wed, May 27, 2020 at 12:59:24PM -0500, Mario Frasca wrote: > myself, I recently posted a patch, received zero reaction, and have the > impression it's now lost in the logs of this mailing list.  indeed > pretty inefficient! Or the devs haven't had a chance yet. > something which flashed to my

Re: issue tracker?

report-emacs-bug? cheers, MF On 19/05/2020 09:58, Bruce D'Arcus wrote: Regardless, doing issue tracking, discussion, and patch submission on a ML in 2020 is pretty odd and inefficient. I would have submitted feedback here 6-12 months earlier than I did if org had a proper issue tracker.

Re: issue tracker?

Anthony Carrico writes: > Given that the mailing list holds the issues, it would be nice if you > could import the mailing list into your client as a lump (maildir/mbox). > Currently you can only download it chunk by chunk, so it isn't really > practical for a newcomer to import the whole

Re: issue tracker?

Detlef Steuer writes: > How to add more now? Same here. Mail is functionally superior to a lot > of modern solutions. > > A Bugtracker you do not use on a regular basis often is a horrible time sink. > Plus, most of the time you need just another account for a site you > never wanted an account

Re: issue tracker?

> On Mon, 25 May 2020 13:20:30 +0200, Roland Everaert > said: Roland> No, I was not aware of it. Yet, if I understand the objective of the Emacs Roland> ML and Debbugs, it is for, when you have a crash with emacs or, at least, Roland> an error stack trace when evaluating

Re: issue tracker?

No, I was not aware of it. Yet, if I understand the objective of the Emacs ML and Debbugs, it is for, when you have a crash with emacs or, at least, an error stack trace when evaluating some lisp code. This is different from the intent here to define how to switch a thread started as a simple

Re: issue tracker?

On Sat, May 23, 2020 at 02:57:26PM +0200, Roland Everaert wrote: > There must be also some kind of "protocol" to transition between the > various discussions, like > - from bug to a normal question > - normal question to a feature request > You are aware this is how the Emacs bug mailing list

Re: issue tracker?

I have to admit that I am kind of a state tracking freak, so, your proposal is welcomed to keep that tendency at bay. However, I would add a "category" for bugs/issues and feature requests, in the subject, else, the bot, the readers and the maintainer will have still to dig deep into threads to

Re: issue tracker?

On Wed, May 20, 2020 at 7:36 PM Anthony Carrico wrote: > Given that the mailing list holds the issues, it would be nice if you > could import the mailing list into your client as a lump (maildir/mbox). > Currently you can only download it chunk by chunk, so it isn't really > practical for a

Re: issue tracker?

On 5/22/20 4:17 AM, Roland Everaert wrote: Example of message states: [QUESTION] -> [ANSWER] [BUG] -> ( [CONFIRMED] | [WONTFIX] | [SOLVED] ) [CONFIRMED] -> ( [SOLVED] | [PLANNED] ) [FEATURE] -> ( [WONTDO] | [PLANNED] | [IMPLEMENTED] ) [PLANNED] -> ( [IMPLEMENTED] | [SOLVED] ) I love your

Re: issue tracker?

I will surely state the obvious, but the output of this discussion is that ther4e is a need for everybody, what ever our relationship to org-mode or emacs, needs a way to filter the various conversation about org-mode on the various communication channel used by the project. This mainly imply

Re: issue tracker?

Kévin Le Gouguec writes: > Nicolas Goaziou writes: > >> - As pointed out, Org has a bug tracker : Emacs' Debbugs. See >> . Org users do not send bugs >> through it much. > > (In the event that they do, should whoever follows bug-gnu-emacs refer > these

Re: issue tracker?

Anthony Carrico writes: > On 5/21/20 10:18 AM, Anthony Carrico wrote: >> which is a big ask for users. > > ... given that the community expressed that it would like to interact on > a mailing list without other user facing tooling. AFAICT, the only thing users have to do to participate in

Re: issue tracker?

Nicolas Goaziou writes: > - As pointed out, Org has a bug tracker : Emacs' Debbugs. See > . Org users do not send bugs > through it much. (In the event that they do, should whoever follows bug-gnu-emacs refer these users to emacs-orgmode?) > -

Re: issue tracker?

On 5/21/20 10:18 AM, Anthony Carrico wrote: > which is a big ask for users. ... given that the community expressed that it would like to interact on a mailing list without other user facing tooling. -- Anthony Carrico

Re: issue tracker?

On Thu, May 21, 2020 at 10:18:27AM -0400, Anthony Carrico wrote: > On 5/21/20 3:31 AM, Kévin Le Gouguec wrote: > > I think you've just described, in order: > > > > - Debbugs (the issue tracking software), > > Yes, I almost mentioned that Debian uses an email based bug tracker, as > a point of

Re: issue tracker?

On 5/21/20 3:31 AM, Kévin Le Gouguec wrote: > I think you've just described, in order: > > - Debbugs (the issue tracking software), Yes, I almost mentioned that Debian uses an email based bug tracker, as a point of reference. I'm not familiar with the details, but I think it is header based,

Re: issue tracker?

On Thu, May 21, 2020 at 4:11 AM Nicolas Goaziou wrote: ... > - Debbugs has a nice, modern, front end, too: Mumi > (). See for > example . That'd be a nice improvement. Bruce

Re: issue tracker?

Hello, Detlef Steuer writes: > That leads to the next point: If Nicolas decided *he* would love to work > with a bugtracker, I would not complain and open an account. > As it is now, anything that's not in the best interest of our benevolent > developer, should not even be considered :-) Thank

Re: issue tracker?

"James R Miller" writes: >> I think issue tracking could happen on a mailing list. If you tag an >> issue's subject line with OPEN: or CLOSE:, a bot could mail a summary of >> the OPEN: issues to the list periodically (in theory). > > Something like that would be nice; the bot could even store

Re: issue tracker?

On Wed, May 20, 2020 at 10:12:38PM -0500, James R Miller wrote: > > I think issue tracking could happen on a mailing list. If you tag an > > issue's subject line with OPEN: or CLOSE:, a bot could mail a summary of > > the OPEN: issues to the list periodically (in theory). > > Something like that

Re: issue tracker?

> I think issue tracking could happen on a mailing list. If you tag an > issue's subject line with OPEN: or CLOSE:, a bot could mail a summary of > the OPEN: issues to the list periodically (in theory). Something like that would be nice; the bot could even store such info in an org file that

Re: issue tracker?

On 5/18/20 5:24 PM, Anthony Carrico wrote: Does org-mode have an issue tracker, to keep track of which issues are active, or is it just this mailing list? I'm the OP here. My first post to this list generated a lot of feedback. I'm not sure I have an opinion, it was an honest question

Re: issue tracker?

Aloha everyone, Sometimes a "lower tech" solution is best, or at least offers a lot of advantages. What I see as the advantages of resolving issues through a mailing list are: * Minimal barriers to entry. If you have an email client of ANY type, you're in. No need for anything more. I think

RE: issue tracker?

day, 20 May, 2020 12:42 To: Stefan Nobis Cc: emacs-orgmode@gnu.org Subject: Re: issue tracker? I second that. Nicolas, thank you! Great product, better vision, high energy! ‐‐‐ Original Message ‐‐‐ On Wednesday, May 20, 2020 7:12 AM, Stefan Nobis wrote: > Detlef Steuer

Re: issue tracker?

I second that. Nicolas, thank you! Great product, better vision, high energy! ‐‐‐ Original Message ‐‐‐ On Wednesday, May 20, 2020 7:12 AM, Stefan Nobis wrote: > Detlef Steuer ste...@hsu-hh.de writes: > > > I would go as far as saying this list is one of the fastest > > reacting

Re: issue tracker?

Detlef Steuer writes: > I would go as far as saying *this list* is one of the fastest > reacting amd friendliest communities I have been part of. The job > Nicolas does is just awesome. +1! -- Until the next mail..., Stefan.

Re: issue tracker?

Am Wed, 20 May 2020 10:22:56 +0100 schrieb Eric S Fraga : > On Tuesday, 19 May 2020 at 18:57, Russell Adams wrote: > > My personal opinion is I'd always prefer to use my mail client over > > some website. > > +∞! How to add more now? Same here. Mail is functionally superior to a lot of

Re: issue tracker?

On Tuesday, 19 May 2020 at 18:57, Russell Adams wrote: > My personal opinion is I'd always prefer to use my mail client over some > website. +∞! There are some communities that I would love to participate in but do not because they use, for instance, discourse which has a horrible email

Re: issue tracker?

d with the ancient (to them) dev practices. I'm not advocating any rash decisions; simply, whether the project would benefit from incorporating some sort of simple issue tracker, so that new contributors could readily see open tasks / issues / submit bug reports. My biggest issue with a ML only approach is

Re: issue tracker?

es The thing is that Sourcehut doesn't really do pull requests, which I think is the tricky part of any "forge". It really is dead simple, and I think would be most useful as a mirror of Org's code, and an issue tracker. Eric

Re: issue tracker?

On 5/19/2020 1:48 PM, Russell Adams wrote: > On Tue, May 19, 2020 at 01:50:26PM -0500, James R Miller wrote: >> I think an actual issue tracker has merit to large projects. >> >> And I don't think simply saying "we've always done it through a ML" or "$FOO >&g

Re: issue tracker?

; "James R Miller" writes: >> >> > So, I definitely agree that using Github / Gitlab does expose you to >> > tracking messes and that is something to shun. I figured a self-hosted >> > Gogs instance (which is already being hosted at >> > https://co

Re: issue tracker?

to > > tracking messes and that is something to shun. I figured a self-hosted > > Gogs instance (which is already being hosted at > > https://code.orgmode.org/bzg/org-mode) would fix the "tracking" issue. > > > > I think an actual issue tracker has merit to large proj

Re: issue tracker?

tracker.) I wouldn’t dispute that the Linux kernel ML, for the most part, works. But the Linux kernel mailing list is a rather different beast than the potential users of an issue tracker for any other software project I can imagine—the technical acumen expected of contributors is high, quotidia

Re: issue tracker?

On Tue, May 19, 2020 at 01:50:26PM -0500, James R Miller wrote: > I think an actual issue tracker has merit to large projects. > > And I don't think simply saying "we've always done it through a ML" or "$FOO > project is bigger than us and uses a ML" is good enou

Re: issue tracker?

x the "tracking" issue. > > I think an actual issue tracker has merit to large projects. I've been going around doing proselytizing for sr.ht (sourcehut, aka "Sir Hat"), which is a forge-like site that is very much in line with Emacs' principles. No tracking (barely any javasc

Re: issue tracker?

So, I definitely agree that using Github / Gitlab does expose you to tracking messes and that is something to shun. I figured a self-hosted Gogs instance (which is already being hosted at https://code.orgmode.org/bzg/org-mode) would fix the "tracking" issue. I think an actual issue t

Re: issue tracker?

of both worlds, is there a > reason why we'd say no? Just taking a guess here, but I imagine it > should be possible to sync up a public issue tracker to the mailing list. I can't object to different viewers of list content. It's archived in many places already, and perhaps those interfaces could filte

Re: issue tracker?

it should be possible to sync up a public issue tracker to the mailing list. I may have missed something, or be barking up the wrong tree, but those are my current thoughts :) On May 20 2020, at 12:57 am, Russell Adams wrote: > I can't help but chime in here. Using email for project management, patc

Re: issue tracker?

ing issue tracking, discussion, and patch submission on a ML > in 2020 is pretty odd and inefficient. > > I would have submitted feedback here 6-12 months earlier than I did if org > had a proper issue tracker. > > On Tue, May 19, 2020, 3:35 AM wrote: > > > On Mon, Ma

Re: issue tracker?

My 2c: Having a github-esque pubic issue tracker is good for accessibility — in the sense of ease of access to new-comers. Personally, this is the first time I've engaged in technical discussions on a mailing list, and needing to use a ML did feel like an extra hurdle. I wouldn't imagine

Re: issue tracker?

Regardless, doing issue tracking, discussion, and patch submission on a ML in 2020 is pretty odd and inefficient. I would have submitted feedback here 6-12 months earlier than I did if org had a proper issue tracker. On Tue, May 19, 2020, 3:35 AM wrote: > On Mon, May 18, 2020 at 06:13:3

Re: issue tracker?

On Tue, May 19, 2020 at 09:05:33AM -0500, James R Miller wrote: > (I also don’t understand the knee jerk response away from > cookies / JavaScript). Mine isn't a knee-jerk reaction. It's worse: it's well thought-out. Discussing that in detail would be far off-topic for this list, though. > Those

Re: issue tracker?

(I also don’t understand the knee jerk response away from cookies / JavaScript). Those are just parts of the modern web... Cookies for state and persistent login and JavaScript for making the web page interactive. Are you saying you’d want some sort of REST api instead and the website would

Re: issue tracker?

My apologies. I thought Gogs was the repository for org as I that is what is linked from the homepage. -- James Miller james.ryland.mil...@gmail.com

Re: issue tracker?

On Mon, May 18, 2020 at 06:13:38PM -0500, James R Miller wrote: > Doesn’t Gogs have a nice issue tracker functionality? I looked up Gogs. Needs javascript *and* cookies. Wake me up when there's a plain, straight service which works without any of them. Cheers -- t signature.asc Descript

Re: issue tracker?

Doesn’t Gogs have a nice issue tracker functionality? -- James Miller james.ryland.mil...@gmail.com

Re: issue tracker?

Anthony Carrico writes: > Does org-mode have an issue tracker, to keep track of which issues are > active, or is it just this mailing list? Just this mailing list. -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by

issue tracker?

Does org-mode have an issue tracker, to keep track of which issues are active, or is it just this mailing list? -- Anthony Carrico

Re: [O] Org mode issue tracker

Brett Viren b...@bnl.gov writes: Hi, Hi Brett, * TODO Subject timestamp :emacs_ver:org_ver:org_module: ... Emacs version ends up as a tag: * TODO . :24.3: Or, if I add an Org version: * TODO .

Re: [O] Org mode issue tracker

Hi Suvayu, What a nice work you've done... Some comments... Suvayu Ali wrote: This is the general structure I'm proposing: * TODO Subject timestamp :emacs_ver:org_ver:org_module: :PROPERTIES: :DEBGUGS_ID: bug number :REPORTER:Reporter Name :CC_EMAIL:

Re: [O] Org mode issue tracker

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]. Doesn't the

Re: [O] Org mode issue tracker

On Thu, Sep 26, 2013 at 10:22 AM, Suvayu Ali fatkasuvayu+li...@gmail.com 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

Re: [O] Org mode issue tracker

Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org 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

Re: [O] Org mode issue tracker

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 Tue]. Doesn't the

Re: [O] Org mode issue tracker

Hello Michael, On Thu, Sep 26, 2013 at 11:34:31AM +0200, Michael Albinus wrote: Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: ((source . unknown) (found_versions 24.3) Emacs version ends up as a tag: * TODO .

Re: [O] Org mode issue tracker

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 . The body

Re: [O] Org mode issue tracker

Suvayu Ali fatkasuvayu+li...@gmail.com 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

Re: [O] Org mode issue tracker

-2 BTW, I think an issue tracker in Org is very interesting. I look forward to seeing how it evolves. -Brett. pgp6kwuMSCpiV.pgp Description: PGP signature

[O] Org mode issue tracker

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

Re: [O] Org mode issue tracker

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

Re: [O] Org mode issue tracker

On 25.9.2013, at 09:28, Christian Moe m...@christianmoe.com 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

Re: [O] Org mode issue tracker

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

Re: [O] Org mode issue tracker

On 25.9.2013, at 09:51, Sebastien Vauban sva-n...@mygooglest.com 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

Re: [O] Org mode issue tracker

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 idea.

Re: [O] Org mode issue tracker

On 25.9.2013, at 08:43, Carsten Dominik carsten.domi...@gmail.com 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

Re: [O] Org mode issue tracker

Carsten Dominik wrote: On 25.9.2013, at 09:51, Sebastien Vauban sva-n...@mygooglest.com 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

Re: [O] Org mode issue tracker

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 natural too!

Re: [O] Org mode issue tracker

of the Universe *except his own*, three times over,) - Carsten On 25.9.2013, at 11:04, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: On 25.9.2013, at 09:51, Sebastien Vauban sva-n...@mygooglest.com wrote: Carsten Dominik wrote: we do not have an issue tracker for Org

Re: [O] Org mode issue tracker

package on ELPA. The frontend, debbugs-gnu, allows to filter for packages and tags. Try (debbugs-gnu '(serious important normal) '(org-mode)) On my wannabe todo list is a package debbugs-org.el, which shows the entries as TODO items. If the org community decides to use debbugs as issue tracker

Re: [O] Org mode issue tracker

). On my wannabe todo list is a package debbugs-org.el, which shows the entries as TODO items. If the org community decides to use debbugs as issue tracker, it would give me a push. I'd find that a promising feature... (I'm not so experienced with org-mode, so I would need at least some

Re: [O] Org mode issue tracker

(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

Re: [O] Org mode issue tracker

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

Re: [O] Org mode issue tracker

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

Re: [O] Org mode issue tracker

Loyall, David david.loy...@nebraska.gov 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:

Re: [O] Org mode issue tracker

Hi Sébastien, Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org 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

Re: [O] Org mode issue tracker

Hello Michael, This is the general structure I'm proposing: * TODO Subject timestamp :emacs_ver:org_ver:org_module: :PROPERTIES: :DEBGUGS_ID: bug number :REPORTER:Reporter Name :CC_EMAIL:list of emails of interested parties :END: I elaborate the ideas