From: Pankaj Jangid <email@example.com> To: Daniele Nicolodi <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Ignored bugs Date: Wed, 18 Nov 2020 08:20:47 +0530 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Daniele Nicolodi's message of "Tue, 17 Nov 2020 20:51:37 +0100") Daniele Nicolodi <firstname.lastname@example.org> writes: > On 17/11/2020 19:41, Boruch Baum wrote: >> A little over a month ago, I submitted several bug reports related to >> org-mode, and sor most of them haven't seen any action whatsoever, not >> even an indication that they were noticed. In many cases, I provided >> either a total solution or a suggested implementation of a solution. >> >> BUG REPORT: 42484 > > I haven't investigated further than reading this email, but the fact > that you are including what look like debbug numbers suggests that you > reported those bugs against Emacs. > > Org is mostly developed outside Emacs and has an independent release > cycle. Emacs syncs irregularly with the latest released version of Org. I was completely unaware of this. I also used to report bugs via emacs' report-emacs-bug fascility. Moreover, I am building emacs from `master' everyday and assuming everything is latest on this. If Org is a different beast then probably we should do two things: 1. Remove Org from built-in packages and distribute only via ELPA 2. And have a completely separate infrastructure for development, mailing-lists, bug reports. This we already have. But we should follow convention so that it is easier for user to report-org-bugs. > Bug report affecting the latest release of Org can be submitted to this > mailing list. This is also the best way to make them known to the Org > developers and maintainer. I don't know how the tracking works if bugs are reported in a mailing list. > I don't think anyone here really looks into > bugs reported to the Emacs debbugs instance: time is limited and the > version of Org distributed with Emacs is very often not the most current > one, thus the bug reports may anyhow not be relevant anyhow. > > I suggest you to try to reproduce these bugs with the latest Org release > (or the latest snapshot from Org ELPA) and report on this list if the > problems persist, see `org-submit-bug-report'. I am trying to use `use-package' for package management via the init file. And when I do (use-package org :ensure t) it doesn't install the latest. It uses the builtin package only. Is this a bug in emacs, use-package or elpa?
next prev parent reply other threads:[~2020-11-18 2:51 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-17 18:41 Boruch Baum 2020-11-17 19:51 ` Daniele Nicolodi 2020-11-17 20:15 ` Boruch Baum 2020-11-17 20:27 ` Daniele Nicolodi 2020-11-17 20:54 ` Boruch Baum 2020-11-17 21:36 ` Jean Louis 2020-11-17 23:42 ` Tim Cross 2020-11-18 4:04 ` Ihor Radchenko 2020-12-14 6:55 ` Bastien 2020-11-18 2:50 ` Pankaj Jangid [this message] 2020-11-18 3:59 ` Tim Cross 2020-11-18 6:44 ` Pankaj Jangid 2020-11-18 6:50 ` Jean Louis 2020-11-18 7:32 ` Tim Cross 2020-11-18 6:03 ` Jean Louis 2020-11-18 6:50 ` Pankaj Jangid 2020-12-14 7:14 ` Bastien
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ email@example.com public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git