Re: Ignored bugs

2020-11-17 Thread Tim Cross
Pankaj Jangid writes: > Tim Cross writes: > >>> 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? >> >>

Re: Ignored bugs

2020-11-17 Thread Jean Louis
* Pankaj Jangid [2020-11-18 09:47]: > Tim Cross writes: > > >> 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

Re: Ignored bugs

2020-11-17 Thread Pankaj Jangid
Jean Louis writes: >> 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

Re: Ignored bugs

2020-11-17 Thread Pankaj Jangid
Tim Cross writes: >> 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? > > Not a bug at all. You have to

Re: Ignored bugs

2020-11-17 Thread Jean Louis
* Pankaj Jangid [2020-11-18 05:51]: > Daniele Nicolodi 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

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Ihor Radchenko
> So from now on, all the DONE tasks would be archived straight away on the > day they are DONE. Not all the tasks, but all the tasks with repeater. > Is there a way to do the same with all the logged items under the :LOGBOOK: > that have been DONE before? It is certainly possible, but require

Re: Ignored bugs

2020-11-17 Thread Ihor Radchenko
> As if that it not acceptable I would then propose these functions: > > M-x report-org-bug > > and > > M-x report-emacs-bug This issue has been discussed in the past in this maillist as well as in the emacs-devel: https://orgmode.org/list/87zhfntkwm@gmail.com/

Re: Ignored bugs

2020-11-17 Thread Tim Cross
Pankaj Jangid writes: > Daniele Nicolodi 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

Re: Ignored bugs

2020-11-17 Thread Pankaj Jangid
Daniele Nicolodi 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

Re: Ignored bugs

2020-11-17 Thread Tim Cross
Jean Louis writes: > > As Org is part of Emacs one has to understand Boruch's point as > valid. This means it is part of Emacs and M-x report-emacs-bug should > not be ignored. Managers of the mailing list or Org developers could > make sure to read those bug reports as well. A cron job to

Re: Ignored bugs

2020-11-17 Thread Jean Louis
* Boruch Baum [2020-11-17 23:57]: > On 2020-11-17 21:27, Daniele Nicolodi wrote: > > The page that introduces the Emacs bug tracker already reports that this > > ... > > The way emacs users behave isn't to go search and find and read that web > page. It's to perform M-x report-emacs-bug. For

Re: Ignored bugs

2020-11-17 Thread Boruch Baum
On 2020-11-17 21:27, Daniele Nicolodi wrote: > The page that introduces the Emacs bug tracker already reports that this > ... The way emacs users behave isn't to go search and find and read that web page. It's to perform M-x report-emacs-bug. For people using a command completion program, while

Re: Ignored bugs

2020-11-17 Thread Daniele Nicolodi
On 17/11/2020 21:15, Boruch Baum wrote: > On 2020-11-17 20:51, Daniele Nicolodi wrote: >> Please complain with the Emacs maintainers about their handling of the >> bugs on the Emacs bug tracking system, > > How do I know it was "their handling" and not "your handling"? It's > unclear from my view

Re: Ignored bugs

2020-11-17 Thread Boruch Baum
On 2020-11-17 20:51, Daniele Nicolodi wrote: > Please complain with the Emacs maintainers about their handling of the > bugs on the Emacs bug tracking system, How do I know it was "their handling" and not "your handling"? It's unclear from my view of the thread who performed the actions but all

Re: Ignored bugs

2020-11-17 Thread Daniele Nicolodi
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

Ignored bugs

2020-11-17 Thread Boruch Baum
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

[PATCH] Remove redundant 'function's around lambda

2020-11-17 Thread Stefan Kangas
I've been working on removing redundant `function' around `lambda' in Emacs core, so here is a patch which does the same for Org-mode. Note that Info node `(elisp) Anonymous Functions' says that: The read syntax ‘#'’ is a short-hand for using ‘function’. The following forms are all

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Robert Pluim
"Dr. Arne Babenhauserheide" writes: > I have seen no uproar here. Discussions here were friendly and > constructive. The discusssions are long, because there aren’t easy > solutions to managing changes in UX in central places. > > And a significant share of the discussion was about the question

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Gerardo Moro
Thank you! Ok, now it works. I had to restart my Emacs, probably that was the problem. So from now on, all the DONE tasks would be archived straight away on the day they are DONE. What about the previously LOGGED tasks? Is there a way to do the same with all the logged items under the :LOGBOOK:

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Ihor Radchenko
> Now I get the error: "wrong number of arguments..." :D It does not happen in my Emacs. It would be helpful if you shared the whole error message. I used the following code for testing: (defun my/org-archive-without-delete () "Archive item at point, but do not actually delete it." (cl-letf

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Gerardo Moro
Now I get the error: "wrong number of arguments..." :D El mar., 17 nov. 2020 a las 15:13, Ihor Radchenko () escribió: > > I tried this but I get: "symbol's function definition is void: > > org-trigger-doing" > > Oops. That's the old function name. Should be > > (add-hook 'org-trigger-hook

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Maxim Nikulin
2020-11-16 Dr. Arne Babenhauserheide wrote: I would like to agree, because I wish people would also read NEWS for my projects, but since I use at least 10-20 programs daily which depend on hundreds of libraries that might change their behavior, that’s unrealistic. I cannot read NEWS entries

patch to add mention of org-table-transpose-table-at-point to doc

2020-11-17 Thread Greg Minshall
hi. this adds the minimal mention of transpose. cheers. diff --git a/doc/org-manual.org b/doc/org-manual.org index 040fccc21..33d32b8f5 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -1649,6 +1649,12 @@ you, configure the option ~org-table-auto-blank-field~. the buffer. You

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Dr. Arne Babenhauserheide
Stefan Nobis writes: > "Dr. Arne Babenhauserheide" writes: > >> Sad story short:... > > I'm with you - last weekend I upgrade my OS and had quite some trouble > to get everything working again and still have some nasty hoops to > jump through. > > But on the other side: … … > I'm really

Re: patch to change org-adapt-indentation customization documentation

2020-11-17 Thread Greg Minshall
Robert, > The whole point of customize is that you shouldn't have to worry about > what the actual lisp value is. The actual lisp value only matters if > you directly set the value without using customize. thanks for the response. i've included the documentation for org-adapt-indentation below.

Re: patch to change org-adapt-indentation customization documentation

2020-11-17 Thread Robert Pluim
Greg Minshall writes: > for some reason, i was motivated to look at changing > org-adapt-indentation. i found that the help text talked about values > t, 'headline-data, and nil, but that the customization text didn't > (though, of course, it *set* those values). the following might make it >

patch to change org-adapt-indentation customization documentation

2020-11-17 Thread Greg Minshall
for some reason, i was motivated to look at changing org-adapt-indentation. i found that the help text talked about values t, 'headline-data, and nil, but that the customization text didn't (though, of course, it *set* those values). the following might make it clearer. diff --git a/lisp/org.el

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Greg Minshall
Tim, thanks. my tests were in a src block inside the main buffer. like you, i normally edit in an Org Src... buffer. but, it's nice when it basically "works" even in the main buffer (for minor edits, etc.). and, yes, setting org-adapt-indentation to either 'headline-data or nil seems likely

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Ihor Radchenko
> I tried this but I get: "symbol's function definition is void: > org-trigger-doing" Oops. That's the old function name. Should be (add-hook 'org-trigger-hook #'org-archive-repeated-task) Best, Ihor Gerardo Moro writes: > Thanks for the prompt reply! > I tried this but I get: "symbol's

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Gerardo Moro
Thanks for the prompt reply! I tried this but I get: "symbol's function definition is void: org-trigger-doing" El mar., 17 nov. 2020 a las 14:32, Ihor Radchenko () escribió: > > Thanks, I don't know how to go about doing that, so I would have to rely > on > > others wanting to help me if they

Re: default :results

2020-11-17 Thread ian martins
On Sat, Nov 14, 2020 at 5:27 AM ian martins wrote: > > On Wed, Nov 11, 2020 at 3:04 AM Bastien wrote: > > > > The default for ob-shell execution was to use the output, not the > > value. Then we had a long discussion, leading to this: > > > > - The default (no :result) is to display the

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Ihor Radchenko
> Thanks, I don't know how to go about doing that, so I would have to rely on > others wanting to help me if they consider this to be also useful to them > (which I definitely think it is!). Try the following code. It should archive any repeated task once it is marked DONE. (defun

Re: [PATCH] ob-java

2020-11-17 Thread ian martins
On Sat, Nov 14, 2020 at 6:48 AM Jarmo Hurri wrote: > > >> > It seems that you have changed some classloader settings in the new > >> > code. I have examples which used to work perfectly; now they still > >> > compile, but fail to run, throwing exception > >> > > >> >

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Gerardo Moro
Thanks, I don't know how to go about doing that, so I would have to rely on others wanting to help me if they consider this to be also useful to them (which I definitely think it is!). El mar., 17 nov. 2020 a las 11:32, Ihor Radchenko () escribió: > > I actually now realized that your function

Re: Bug: Can't toggle off archived tasks in agenda with "v A" [9.4 (9.4-41-g9bb930-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20201116/)]

2020-11-17 Thread Gustavo Barros
On Tue, 17 Nov 2020 at 02:54, Kyle Meyer wrote: Gustavo Barros writes: Hi All, The toggling of Archives mode in the agenda, the one which includes archive files, called with "v A", can be turned on, but turning it off with "v A" does not currently work. An ECM to reproduce the issue

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Jean Louis
* Detlef Steuer [2020-11-17 11:47]: :PROPERTIES: :CREATED: [2020-11-17 Tue 12:41] :ID: 2bc18302-d009-4751-b062-b3cf2aa44d18 :END: > It is *impossible* to force users to be informed. Think about us: We > all hang around on this list and missed the information. What would > reasonably be

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Ihor Radchenko
> I actually now realized that your function will not unfortunately archive > each logged item (those located in the logbook) in its corresponding date > (!). > What it will do is to archive the whole tree under today's date without > deleting it from the original org file. You are right. It is

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Diego Zamboni
On Tue, Nov 17, 2020 at 10:06 AM Stefan Nobis wrote: > But on the other side: What are we talking about? > ... > But ranting so loudly and insistent and continuously over such a minor > details is really beyond me. > ... > So, everyone, please calm down and try not to overreact over really >

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Loris Bennett
Stefan Nobis writes: > "Dr. Arne Babenhauserheide" writes: > >> Sad story short:... > > I'm with you - last weekend I upgrade my OS and had quite some trouble > to get everything working again and still have some nasty hoops to > jump through. > > But on the other side: What are we talking

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Stefan Nobis
"Dr. Arne Babenhauserheide" writes: > Sad story short:... I'm with you - last weekend I upgrade my OS and had quite some trouble to get everything working again and still have some nasty hoops to jump through. But on the other side: What are we talking about? Org had a given default

Re: Archiving repeated tasks under corresponding date tree for each repeated item

2020-11-17 Thread Gerardo Moro
Hi again, I actually now realized that your function will not unfortunately archive each logged item (those located in the logbook) in its corresponding date (!). What it will do is to archive the whole tree under today's date without deleting it from the original org file. For instance, * TODO

Re: Changed list indentation behavior: how to revert?

2020-11-17 Thread Detlef Steuer
Am Tue, 17 Nov 2020 01:11:38 +0100 schrieb "Dr. Arne Babenhauserheide" : > The only way that works is to avoid breakage on update — except for > the few cases where it is truly unavoidable. Well, and as long as the change can be reverted when the community has a thoughtful discussion with those

Re: Re: Agenda follow mode + indirect window settings

2020-11-17 Thread Gerardo Moro
Very nice! I don't know much elisp as I am a new Emacs user. What in short would this code do? :) Thanks a million! El mar., 17 nov. 2020 a las 6:56, tumashu () escribió: > > > > > > > > > > > > > > > > > > At 2020-11-17 12:52:06, "Kyle Meyer" wrote: > >Gerardo Moro writes: > > > >> Hi, > >> >

Re: Agenda follow mode + indirect window settings

2020-11-17 Thread Gerardo Moro
Thanks a lot for this. Will think about it. El mar., 17 nov. 2020 a las 6:52, Kyle Meyer () escribió: > Gerardo Moro writes: > > > Hi, > > > > I want my agenda to have follow-mode active when starting Emacs. > > I suppose this would do the trick? > > > > (setq org-agenda-start-with-follow-mode