Package cl is deprecated

Package cl is deprecated

[Hongyi Zhao]

When I start Emacs, I always notice the following message in *Messages* buffer:

Package cl is deprecated

Any hints for eliminating it?

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Jean Louis]

* Hongyi Zhao <hongyi.zhao@gmail.com> [2021-07-28 12:25]:
> When I start Emacs, I always notice the following message in *Messages* buffer:
> 
> Package cl is deprecated
> 
> Any hints for eliminating it?

Probably some of packages you are loading is using the deprecated
Emacs Lisp library `cl' after version 27.1

Way to go is to find out which package uses `cl' library and then to
inform the author to switch to `cl-lib'

Or you could change `cl' to `cl-lib' in those packages yourself and
try to see if it works without warning.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

Re: Package cl is deprecated

[Thibaut Verron]

On 28/07/2021 11:23, Hongyi Zhao wrote:
> When I start Emacs, I always notice the following message in *Messages* buffer:
>
> Package cl is deprecated
>
> Any hints for eliminating it?

If you have (require 'cl) somewhere in your init file, replace it with 
(require 'cl-lib). You might need to change some macro calls to use 
cl-<name> instead of <name>.

If you don't have the (require 'cl) in your init file, you should 
identify the package which loads the old library and report the warning 
as a bug.

More details: https://emacs.stackexchange.com/a/48115/184

Best wishes,

Thibaut

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>
> On 28/07/2021 11:23, Hongyi Zhao wrote:
> > When I start Emacs, I always notice the following message in *Messages* buffer:
> >
> > Package cl is deprecated
> >
> > Any hints for eliminating it?
>
> If you have (require 'cl) somewhere in your init file, replace it with
> (require 'cl-lib). You might need to change some macro calls to use
> cl-<name> instead of <name>.

$ egrep 'require[ ]*'\''cl' .emacs.d/init.el
(require 'cl-lib)

> If you don't have the (require 'cl) in your init file, you should
> identify the package which loads the old library and report the warning
> as a bug.
>
> More details: https://emacs.stackexchange.com/a/48115/184
>
> Best wishes,
>
> Thibaut
>


-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Thibaut Verron]

On 28/07/2021 11:46, Hongyi Zhao wrote:
> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>> On 28/07/2021 11:23, Hongyi Zhao wrote:
>>> When I start Emacs, I always notice the following message in *Messages* buffer:
>>>
>>> Package cl is deprecated
>>>
>>> Any hints for eliminating it?
>> If you have (require 'cl) somewhere in your init file, replace it with
>> (require 'cl-lib). You might need to change some macro calls to use
>> cl-<name> instead of <name>.
> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
> (require 'cl-lib)

Then it's from a package and you need to identify it.

You can try (untested):

find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;

But I'm sure there is an easier way to do it from within emacs.

Best wishes,

Thibaut

Re: Package cl is deprecated

[Jean-Christophe Helary]

> On Jul 28, 2021, at 18:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
> 
> On 28/07/2021 11:46, Hongyi Zhao wrote:
>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
>>>> 
>>>> Package cl is deprecated
>>>> 
>>>> Any hints for eliminating it?
>>> If you have (require 'cl) somewhere in your init file, replace it with
>>> (require 'cl-lib). You might need to change some macro calls to use
>>> cl-<name> instead of <name>.
>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
>> (require 'cl-lib)
> 
> Then it's from a package and you need to identify it.
> 
> You can try (untested):
> 
> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;

find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; -print


-- 
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/

Re: Package cl is deprecated

[Leo Butler]

>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
>>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
>>>>> 
>>>>> Package cl is deprecated
>>>>> 
>>>>> Any hints for eliminating it?

Put something like

(debug-on-message "Package cl is deprecated")

at the top of your .emacs file, then start a fresh emacs instance.

Ref.

(Info-index "debug-on-message")

Leo

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
<lists@traduction-libre.org> wrote:
>
>
>
> > On Jul 28, 2021, at 18:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >
> > On 28/07/2021 11:46, Hongyi Zhao wrote:
> >> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >>> On 28/07/2021 11:23, Hongyi Zhao wrote:
> >>>> When I start Emacs, I always notice the following message in *Messages* buffer:
> >>>>
> >>>> Package cl is deprecated
> >>>>
> >>>> Any hints for eliminating it?
> >>> If you have (require 'cl) somewhere in your init file, replace it with
> >>> (require 'cl-lib). You might need to change some macro calls to use
> >>> cl-<name> instead of <name>.
> >> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
> >> (require 'cl-lib)
> >
> > Then it's from a package and you need to identify it.
> >
> > You can try (untested):
> >
> > find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
>
> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; -print

There are so many matches:

$ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
-print 2>/dev/null | sort -u | wc -l
40

So this method is basically useless for finding the problem.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Thibaut Verron]

On 28/07/2021 15:03, Hongyi Zhao wrote:
> On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
> <lists@traduction-libre.org> wrote:
>>
>>
>>> On Jul 28, 2021, at 18:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>>
>>> On 28/07/2021 11:46, Hongyi Zhao wrote:
>>>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
>>>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
>>>>>>
>>>>>> Package cl is deprecated
>>>>>>
>>>>>> Any hints for eliminating it?
>>>>> If you have (require 'cl) somewhere in your init file, replace it with
>>>>> (require 'cl-lib). You might need to change some macro calls to use
>>>>> cl-<name> instead of <name>.
>>>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
>>>> (require 'cl-lib)
>>> Then it's from a package and you need to identify it.
>>>
>>> You can try (untested):
>>>
>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; -print
> There are so many matches:
>
> $ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
> -print 2>/dev/null | sort -u | wc -l
> 40
>
> So this method is basically useless for finding the problem.

I just tried it, indeed quite a few packages contain some form of 
(require 'cl) as a backward-compatibility tool (52 matches in my case). 
Most of those are test files which are never loaded in a normal emacs 
session.

To narrow the search, you can use egrep -q "^\(require 'cl\)" instead. 
In my .emacs, the matches go from 52 to 15. Interestingly enough, 
exactly one of them is loaded at init time (key-combo.el), without any 
warning.

[Btw I don't think that sort -u is useful in your command line, find 
should not return the same file twice. You might also want to add -type 
f to the find call, to avoid errors with packages with .el in the name 
(such as ansi.el or prescient.el).]

Good luck,

Thibaut

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 9:23 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>
>
> On 28/07/2021 15:03, Hongyi Zhao wrote:
> > On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
> > <lists@traduction-libre.org> wrote:
> >>
> >>
> >>> On Jul 28, 2021, at 18:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >>>
> >>> On 28/07/2021 11:46, Hongyi Zhao wrote:
> >>>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
> >>>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
> >>>>>>
> >>>>>> Package cl is deprecated
> >>>>>>
> >>>>>> Any hints for eliminating it?
> >>>>> If you have (require 'cl) somewhere in your init file, replace it with
> >>>>> (require 'cl-lib). You might need to change some macro calls to use
> >>>>> cl-<name> instead of <name>.
> >>>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
> >>>> (require 'cl-lib)
> >>> Then it's from a package and you need to identify it.
> >>>
> >>> You can try (untested):
> >>>
> >>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
> >> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; -print
> > There are so many matches:
> >
> > $ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
> > -print 2>/dev/null | sort -u | wc -l
> > 40
> >
> > So this method is basically useless for finding the problem.
>
> I just tried it, indeed quite a few packages contain some form of
> (require 'cl) as a backward-compatibility tool (52 matches in my case).
> Most of those are test files which are never loaded in a normal emacs
> session.
>
> To narrow the search, you can use egrep -q "^\(require 'cl\)" instead.
> In my .emacs, the matches go from 52 to 15. Interestingly enough,
> exactly one of them is loaded at init time (key-combo.el), without any
> warning.

Strange, I found nothing with this enhanced pattern:

$ find .emacs.d/ -type f -name "*.el" -exec grep -q "^[ ]*\([
]*require[ ]+'cl[ ]*\)" {} \; -print | wc -l
0


> [Btw I don't think that sort -u is useful in your command line, find
> should not return the same file twice. You might also want to add -type
> f to the find call, to avoid errors with packages with .el in the name
> (such as ansi.el or prescient.el).]
>
> Good luck,
>
> Thibaut
>
>


-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 9:33 PM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
>
> On Wed, Jul 28, 2021 at 9:23 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >
> >
> > On 28/07/2021 15:03, Hongyi Zhao wrote:
> > > On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
> > > <lists@traduction-libre.org> wrote:
> > >>
> > >>
> > >>> On Jul 28, 2021, at 18:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
> > >>>
> > >>> On 28/07/2021 11:46, Hongyi Zhao wrote:
> > >>>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
> > >>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
> > >>>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
> > >>>>>>
> > >>>>>> Package cl is deprecated
> > >>>>>>
> > >>>>>> Any hints for eliminating it?
> > >>>>> If you have (require 'cl) somewhere in your init file, replace it with
> > >>>>> (require 'cl-lib). You might need to change some macro calls to use
> > >>>>> cl-<name> instead of <name>.
> > >>>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
> > >>>> (require 'cl-lib)
> > >>> Then it's from a package and you need to identify it.
> > >>>
> > >>> You can try (untested):
> > >>>
> > >>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
> > >> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; -print
> > > There are so many matches:
> > >
> > > $ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
> > > -print 2>/dev/null | sort -u | wc -l
> > > 40
> > >
> > > So this method is basically useless for finding the problem.
> >
> > I just tried it, indeed quite a few packages contain some form of
> > (require 'cl) as a backward-compatibility tool (52 matches in my case).
> > Most of those are test files which are never loaded in a normal emacs
> > session.
> >
> > To narrow the search, you can use egrep -q "^\(require 'cl\)" instead.
> > In my .emacs, the matches go from 52 to 15. Interestingly enough,
> > exactly one of them is loaded at init time (key-combo.el), without any
> > warning.
>
> Strange, I found nothing with this enhanced pattern:
>
> $ find .emacs.d/ -type f -name "*.el" -exec grep -q "^[ ]*\([
> ]*require[ ]+'cl[ ]*\)" {} \; -print | wc -l
> 0

Sorry, egrep should be used:

$ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^[ ]*\([
]*require[ ]+'cl[ ]*\)" {} \; -print | egrep -v  '[/]tests?[/]'
.emacs.d/straight/repos/dash.el/dash.el
.emacs.d/straight/repos/dash.el/dev/examples.el
.emacs.d/straight/repos/stardiviner-sdcv.el/sdcv.el
.emacs.d/straight/repos/showtip/showtip.el
.emacs.d/straight/repos/unicode-escape.el/unicode-escape.el
.emacs.d/straight/repos/use-package/use-package-tests.el
.emacs.d/straight/repos/macrostep/lib/cl-lib.el
.emacs.d/straight/repos/macrostep/lib/ert.el
.emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el
.emacs.d/straight/repos/s.el/dev/ert.el

Regards,
HY

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 7:20 PM Leo Butler <leo.butler@umanitoba.ca> wrote:
>
> >>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
> >>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
> >>>>>
> >>>>> Package cl is deprecated
> >>>>>
> >>>>> Any hints for eliminating it?
>
> Put something like
>
> (debug-on-message "Package cl is deprecated")

I tried this method, but meet the following warning:

Warning (initialization): An error occurred while loading
‘/home/werner/.emacs.d/init.el’:

Symbol's function definition is void: debug-on-message


>
> at the top of your .emacs file, then start a fresh emacs instance.
>
> Ref.
>
> (Info-index "debug-on-message")

`M-: (Info-index "debug-on-message") RET':

Debugger entered--Lisp error: (error "No index")
  signal(error ("No index"))
  error("No index")
  Info-goto-index()
  Info-index("debug-on-message")
  eval((Info-index "debug-on-message") t)
  eval-expression((Info-index "debug-on-message") nil nil 127)
  funcall-interactively(eval-expression (Info-index
"debug-on-message") nil nil 127)
  call-interactively(eval-expression nil nil)
  command-execute(eval-expression)

Hongyi
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Eli Zaretskii]

> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Wed, 28 Jul 2021 21:41:03 +0800
> Cc: Jean-Christophe Helary <lists@traduction-libre.org>,
>  help-gnu-emacs <help-gnu-emacs@gnu.org>,
>  Thibaut Verron <thibaut.verron@gmail.com>
> 
> > (debug-on-message "Package cl is deprecated")
> 
> I tried this method, but meet the following warning:
> 
> Warning (initialization): An error occurred while loading
> ‘/home/werner/.emacs.d/init.el’:
> 
> Symbol's function definition is void: debug-on-message

debug-on-message is a variable, not a function.

> > Ref.
> >
> > (Info-index "debug-on-message")
> 
> `M-: (Info-index "debug-on-message") RET':

This only works in a buffer that shows the Emacs Lisp Reference manual
in Info mode.

Re: Package cl is deprecated

[Thibaut Verron]

On 28/07/2021 15:36, Hongyi Zhao wrote:
> On Wed, Jul 28, 2021 at 9:33 PM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
>> On Wed, Jul 28, 2021 at 9:23 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>>
>>> On 28/07/2021 15:03, Hongyi Zhao wrote:
>>>> On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
>>>> <lists@traduction-libre.org> wrote:
>>>>>
>>>>>> On Jul 28, 2021, at 18:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>>>>>
>>>>>> On 28/07/2021 11:46, Hongyi Zhao wrote:
>>>>>>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>>>>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
>>>>>>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
>>>>>>>>>
>>>>>>>>> Package cl is deprecated
>>>>>>>>>
>>>>>>>>> Any hints for eliminating it?
>>>>>>>> If you have (require 'cl) somewhere in your init file, replace it with
>>>>>>>> (require 'cl-lib). You might need to change some macro calls to use
>>>>>>>> cl-<name> instead of <name>.
>>>>>>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
>>>>>>> (require 'cl-lib)
>>>>>> Then it's from a package and you need to identify it.
>>>>>>
>>>>>> You can try (untested):
>>>>>>
>>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; -print
>>>> There are so many matches:
>>>>
>>>> $ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
>>>> -print 2>/dev/null | sort -u | wc -l
>>>> 40
>>>>
>>>> So this method is basically useless for finding the problem.
>>> I just tried it, indeed quite a few packages contain some form of
>>> (require 'cl) as a backward-compatibility tool (52 matches in my case).
>>> Most of those are test files which are never loaded in a normal emacs
>>> session.
>>>
>>> To narrow the search, you can use egrep -q "^\(require 'cl\)" instead.
>>> In my .emacs, the matches go from 52 to 15. Interestingly enough,
>>> exactly one of them is loaded at init time (key-combo.el), without any
>>> warning.
>> Strange, I found nothing with this enhanced pattern:
>>
>> $ find .emacs.d/ -type f -name "*.el" -exec grep -q "^[ ]*\([
>> ]*require[ ]+'cl[ ]*\)" {} \; -print | wc -l
>> 0
> Sorry, egrep should be used:
>
> $ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^[ ]*\([
> ]*require[ ]+'cl[ ]*\)" {} \; -print | egrep -v  '[/]tests?[/]'
> .emacs.d/straight/repos/dash.el/dash.el
> .emacs.d/straight/repos/dash.el/dev/examples.el
> .emacs.d/straight/repos/stardiviner-sdcv.el/sdcv.el
> .emacs.d/straight/repos/showtip/showtip.el
> .emacs.d/straight/repos/unicode-escape.el/unicode-escape.el
> .emacs.d/straight/repos/use-package/use-package-tests.el
> .emacs.d/straight/repos/macrostep/lib/cl-lib.el
> .emacs.d/straight/repos/macrostep/lib/ert.el
> .emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el
> .emacs.d/straight/repos/s.el/dev/ert.el

The point of the regexp was to exclude files which have something 
(including indentation) before the form, if you allow [ ]* you lose 
that. That's the case in dash.el for example.

In any case, the number of candidates is now small enough that you can 
examine them. The dev/ and lib/ folders can probably be safely ignored to.

Best wishes,

Thibaut

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 9:58 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> > Date: Wed, 28 Jul 2021 21:41:03 +0800
> > Cc: Jean-Christophe Helary <lists@traduction-libre.org>,
> >  help-gnu-emacs <help-gnu-emacs@gnu.org>,
> >  Thibaut Verron <thibaut.verron@gmail.com>
> >
> > > (debug-on-message "Package cl is deprecated")
> >
> > I tried this method, but meet the following warning:
> >
> > Warning (initialization): An error occurred while loading
> > ‘/home/werner/.emacs.d/init.el’:
> >
> > Symbol's function definition is void: debug-on-message
>
> debug-on-message is a variable, not a function.

Then, how to pinpoint the target message?

> > > Ref.
> > >
> > > (Info-index "debug-on-message")
> >
> > `M-: (Info-index "debug-on-message") RET':
>
> This only works in a buffer that shows the Emacs Lisp Reference manual
> in Info mode.

`C-h i RET M-: (Info-index "debug-on-message") RET':

Debugger entered--Lisp error: (error "The Info directory node has no
index; use m to sel...")
  signal(error ("The Info directory node has no index; use m to sel..."))
  error("The Info directory node has no index; use m to sel...")
  Info-index("debug-on-message")
  eval((Info-index "debug-on-message") t)
  eval-expression((Info-index "debug-on-message") nil nil 127)
  funcall-interactively(eval-expression (Info-index
"debug-on-message") nil nil 127)
  call-interactively(eval-expression nil nil)
  command-execute(eval-expression)

Where is my mistake?

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 10:04 PM Thibaut Verron
<thibaut.verron@gmail.com> wrote:
>
> On 28/07/2021 15:36, Hongyi Zhao wrote:
> > On Wed, Jul 28, 2021 at 9:33 PM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
> >> On Wed, Jul 28, 2021 at 9:23 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >>>
> >>> On 28/07/2021 15:03, Hongyi Zhao wrote:
> >>>> On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
> >>>> <lists@traduction-libre.org> wrote:
> >>>>>
> >>>>>> On Jul 28, 2021, at 18:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >>>>>>
> >>>>>> On 28/07/2021 11:46, Hongyi Zhao wrote:
> >>>>>>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >>>>>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
> >>>>>>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
> >>>>>>>>>
> >>>>>>>>> Package cl is deprecated
> >>>>>>>>>
> >>>>>>>>> Any hints for eliminating it?
> >>>>>>>> If you have (require 'cl) somewhere in your init file, replace it with
> >>>>>>>> (require 'cl-lib). You might need to change some macro calls to use
> >>>>>>>> cl-<name> instead of <name>.
> >>>>>>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
> >>>>>>> (require 'cl-lib)
> >>>>>> Then it's from a package and you need to identify it.
> >>>>>>
> >>>>>> You can try (untested):
> >>>>>>
> >>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
> >>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; -print
> >>>> There are so many matches:
> >>>>
> >>>> $ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
> >>>> -print 2>/dev/null | sort -u | wc -l
> >>>> 40
> >>>>
> >>>> So this method is basically useless for finding the problem.
> >>> I just tried it, indeed quite a few packages contain some form of
> >>> (require 'cl) as a backward-compatibility tool (52 matches in my case).
> >>> Most of those are test files which are never loaded in a normal emacs
> >>> session.
> >>>
> >>> To narrow the search, you can use egrep -q "^\(require 'cl\)" instead.
> >>> In my .emacs, the matches go from 52 to 15. Interestingly enough,
> >>> exactly one of them is loaded at init time (key-combo.el), without any
> >>> warning.
> >> Strange, I found nothing with this enhanced pattern:
> >>
> >> $ find .emacs.d/ -type f -name "*.el" -exec grep -q "^[ ]*\([
> >> ]*require[ ]+'cl[ ]*\)" {} \; -print | wc -l
> >> 0
> > Sorry, egrep should be used:
> >
> > $ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^[ ]*\([
> > ]*require[ ]+'cl[ ]*\)" {} \; -print | egrep -v  '[/]tests?[/]'
> > .emacs.d/straight/repos/dash.el/dash.el
> > .emacs.d/straight/repos/dash.el/dev/examples.el
> > .emacs.d/straight/repos/stardiviner-sdcv.el/sdcv.el
> > .emacs.d/straight/repos/showtip/showtip.el
> > .emacs.d/straight/repos/unicode-escape.el/unicode-escape.el
> > .emacs.d/straight/repos/use-package/use-package-tests.el
> > .emacs.d/straight/repos/macrostep/lib/cl-lib.el
> > .emacs.d/straight/repos/macrostep/lib/ert.el
> > .emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el
> > .emacs.d/straight/repos/s.el/dev/ert.el
>
> The point of the regexp was to exclude files which have something
> (including indentation) before the form, if you allow [ ]* you lose
> that. That's the case in dash.el for example.
>
> In any case, the number of candidates is now small enough that you can
> examine them. The dev/ and lib/ folders can probably be safely ignored to.

If so, nothing seems responsible for the problem:

$ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^\(require
'cl\)" {} \; -print |egrep -v  '[/]tests?[/]'
.emacs.d/straight/repos/use-package/use-package-tests.el
.emacs.d/straight/repos/macrostep/lib/cl-lib.el
.emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el

Hongyi
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Leo Butler]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> On Wed, Jul 28, 2021 at 9:58 PM Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
>> > Date: Wed, 28 Jul 2021 21:41:03 +0800
>> > Cc: Jean-Christophe Helary <lists@traduction-libre.org>,
>> >  help-gnu-emacs <help-gnu-emacs@gnu.org>,
>> >  Thibaut Verron <thibaut.verron@gmail.com>
>> >
>> > > (debug-on-message "Package cl is deprecated")
>> >
>> > I tried this method, but meet the following warning:
>> >
>> > Warning (initialization): An error occurred while loading
>> > ‘/home/werner/.emacs.d/init.el’:
>> >
>> > Symbol's function definition is void: debug-on-message
>>
>> debug-on-message is a variable, not a function.
>
> Then, how to pinpoint the target message?

Ahem. I should have written

(setq debug-on-message "Package cl is deprecated")

Ref.

(info "elisp")
(Info-index "debug-on-message")

> Where is my mistake?

As Eli noted, emacs must be in *info* looking at the elisp manual. My
mistake.

Anyhow, debug-on-message will help you isolate the source of the
problem. You may need to play with the regexp ("Package ..."), though.

Leo

Re: Package cl is deprecated

[Thibaut Verron]

On 28/07/2021 16:15, Hongyi Zhao wrote:
> On Wed, Jul 28, 2021 at 10:04 PM Thibaut Verron
> <thibaut.verron@gmail.com> wrote:
>> On 28/07/2021 15:36, Hongyi Zhao wrote:
>>> On Wed, Jul 28, 2021 at 9:33 PM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
>>>> On Wed, Jul 28, 2021 at 9:23 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>>>> On 28/07/2021 15:03, Hongyi Zhao wrote:
>>>>>> On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
>>>>>> <lists@traduction-libre.org> wrote:
>>>>>>>> On Jul 28, 2021, at 18:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>>>>>>>
>>>>>>>> On 28/07/2021 11:46, Hongyi Zhao wrote:
>>>>>>>>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>>>>>>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
>>>>>>>>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
>>>>>>>>>>>
>>>>>>>>>>> Package cl is deprecated
>>>>>>>>>>>
>>>>>>>>>>> Any hints for eliminating it?
>>>>>>>>>> If you have (require 'cl) somewhere in your init file, replace it with
>>>>>>>>>> (require 'cl-lib). You might need to change some macro calls to use
>>>>>>>>>> cl-<name> instead of <name>.
>>>>>>>>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
>>>>>>>>> (require 'cl-lib)
>>>>>>>> Then it's from a package and you need to identify it.
>>>>>>>>
>>>>>>>> You can try (untested):
>>>>>>>>
>>>>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
>>>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; -print
>>>>>> There are so many matches:
>>>>>>
>>>>>> $ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
>>>>>> -print 2>/dev/null | sort -u | wc -l
>>>>>> 40
>>>>>>
>>>>>> So this method is basically useless for finding the problem.
>>>>> I just tried it, indeed quite a few packages contain some form of
>>>>> (require 'cl) as a backward-compatibility tool (52 matches in my case).
>>>>> Most of those are test files which are never loaded in a normal emacs
>>>>> session.
>>>>>
>>>>> To narrow the search, you can use egrep -q "^\(require 'cl\)" instead.
>>>>> In my .emacs, the matches go from 52 to 15. Interestingly enough,
>>>>> exactly one of them is loaded at init time (key-combo.el), without any
>>>>> warning.
>>>> Strange, I found nothing with this enhanced pattern:
>>>>
>>>> $ find .emacs.d/ -type f -name "*.el" -exec grep -q "^[ ]*\([
>>>> ]*require[ ]+'cl[ ]*\)" {} \; -print | wc -l
>>>> 0
>>> Sorry, egrep should be used:
>>>
>>> $ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^[ ]*\([
>>> ]*require[ ]+'cl[ ]*\)" {} \; -print | egrep -v  '[/]tests?[/]'
>>> .emacs.d/straight/repos/dash.el/dash.el
>>> .emacs.d/straight/repos/dash.el/dev/examples.el
>>> .emacs.d/straight/repos/stardiviner-sdcv.el/sdcv.el
>>> .emacs.d/straight/repos/showtip/showtip.el
>>> .emacs.d/straight/repos/unicode-escape.el/unicode-escape.el
>>> .emacs.d/straight/repos/use-package/use-package-tests.el
>>> .emacs.d/straight/repos/macrostep/lib/cl-lib.el
>>> .emacs.d/straight/repos/macrostep/lib/ert.el
>>> .emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el
>>> .emacs.d/straight/repos/s.el/dev/ert.el
>> The point of the regexp was to exclude files which have something
>> (including indentation) before the form, if you allow [ ]* you lose
>> that. That's the case in dash.el for example.
>>
>> In any case, the number of candidates is now small enough that you can
>> examine them. The dev/ and lib/ folders can probably be safely ignored to.
> If so, nothing seems responsible for the problem:
>
> $ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^\(require
> 'cl\)" {} \; -print |egrep -v  '[/]tests?[/]'
> .emacs.d/straight/repos/use-package/use-package-tests.el
> .emacs.d/straight/repos/macrostep/lib/cl-lib.el
> .emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el

Then I guess you will have to check the other candidates, sorry. I'd 
start with the 10 you found above, and then move to the other 30 if 
necessary.

Thibaut

Re: Package cl is deprecated

[Thibaut Verron]

On 28/07/2021 16:23, Thibaut Verron wrote:
> On 28/07/2021 16:15, Hongyi Zhao wrote:
>> On Wed, Jul 28, 2021 at 10:04 PM Thibaut Verron
>> <thibaut.verron@gmail.com> wrote:
>>> On 28/07/2021 15:36, Hongyi Zhao wrote:
>>>> On Wed, Jul 28, 2021 at 9:33 PM Hongyi Zhao <hongyi.zhao@gmail.com> 
>>>> wrote:
>>>>> On Wed, Jul 28, 2021 at 9:23 PM Thibaut Verron 
>>>>> <thibaut.verron@gmail.com> wrote:
>>>>>> On 28/07/2021 15:03, Hongyi Zhao wrote:
>>>>>>> On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
>>>>>>> <lists@traduction-libre.org> wrote:
>>>>>>>>> On Jul 28, 2021, at 18:54, Thibaut Verron 
>>>>>>>>> <thibaut.verron@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> On 28/07/2021 11:46, Hongyi Zhao wrote:
>>>>>>>>>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron 
>>>>>>>>>> <thibaut.verron@gmail.com> wrote:
>>>>>>>>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
>>>>>>>>>>>> When I start Emacs, I always notice the following message 
>>>>>>>>>>>> in *Messages* buffer:
>>>>>>>>>>>>
>>>>>>>>>>>> Package cl is deprecated
>>>>>>>>>>>>
>>>>>>>>>>>> Any hints for eliminating it?
>>>>>>>>>>> If you have (require 'cl) somewhere in your init file, 
>>>>>>>>>>> replace it with
>>>>>>>>>>> (require 'cl-lib). You might need to change some macro calls 
>>>>>>>>>>> to use
>>>>>>>>>>> cl-<name> instead of <name>.
>>>>>>>>>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
>>>>>>>>>> (require 'cl-lib)
>>>>>>>>> Then it's from a package and you need to identify it.
>>>>>>>>>
>>>>>>>>> You can try (untested):
>>>>>>>>>
>>>>>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
>>>>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \; 
>>>>>>>> -print
>>>>>>> There are so many matches:
>>>>>>>
>>>>>>> $ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
>>>>>>> -print 2>/dev/null | sort -u | wc -l
>>>>>>> 40
>>>>>>>
>>>>>>> So this method is basically useless for finding the problem.
>>>>>> I just tried it, indeed quite a few packages contain some form of
>>>>>> (require 'cl) as a backward-compatibility tool (52 matches in my 
>>>>>> case).
>>>>>> Most of those are test files which are never loaded in a normal 
>>>>>> emacs
>>>>>> session.
>>>>>>
>>>>>> To narrow the search, you can use egrep -q "^\(require 'cl\)" 
>>>>>> instead.
>>>>>> In my .emacs, the matches go from 52 to 15. Interestingly enough,
>>>>>> exactly one of them is loaded at init time (key-combo.el), 
>>>>>> without any
>>>>>> warning.
>>>>> Strange, I found nothing with this enhanced pattern:
>>>>>
>>>>> $ find .emacs.d/ -type f -name "*.el" -exec grep -q "^[ ]*\([
>>>>> ]*require[ ]+'cl[ ]*\)" {} \; -print | wc -l
>>>>> 0
>>>> Sorry, egrep should be used:
>>>>
>>>> $ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^[ ]*\([
>>>> ]*require[ ]+'cl[ ]*\)" {} \; -print | egrep -v '[/]tests?[/]'
>>>> .emacs.d/straight/repos/dash.el/dash.el
>>>> .emacs.d/straight/repos/dash.el/dev/examples.el
>>>> .emacs.d/straight/repos/stardiviner-sdcv.el/sdcv.el
>>>> .emacs.d/straight/repos/showtip/showtip.el
>>>> .emacs.d/straight/repos/unicode-escape.el/unicode-escape.el
>>>> .emacs.d/straight/repos/use-package/use-package-tests.el
>>>> .emacs.d/straight/repos/macrostep/lib/cl-lib.el
>>>> .emacs.d/straight/repos/macrostep/lib/ert.el
>>>> .emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el
>>>> .emacs.d/straight/repos/s.el/dev/ert.el
>>> The point of the regexp was to exclude files which have something
>>> (including indentation) before the form, if you allow [ ]* you lose
>>> that. That's the case in dash.el for example.
>>>
>>> In any case, the number of candidates is now small enough that you can
>>> examine them. The dev/ and lib/ folders can probably be safely 
>>> ignored to.
>> If so, nothing seems responsible for the problem:
>>
>> $ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^\(require
>> 'cl\)" {} \; -print |egrep -v  '[/]tests?[/]'
>> .emacs.d/straight/repos/use-package/use-package-tests.el
>> .emacs.d/straight/repos/macrostep/lib/cl-lib.el
>> .emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el
>
> Then I guess you will have to check the other candidates, sorry. I'd 
> start with the 10 you found above, and then move to the other 30 if 
> necessary.

showtip.el is one.

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 10:25 PM Thibaut Verron
<thibaut.verron@gmail.com> wrote:
>
>
> On 28/07/2021 16:23, Thibaut Verron wrote:
> > On 28/07/2021 16:15, Hongyi Zhao wrote:
> >> On Wed, Jul 28, 2021 at 10:04 PM Thibaut Verron
> >> <thibaut.verron@gmail.com> wrote:
> >>> On 28/07/2021 15:36, Hongyi Zhao wrote:
> >>>> On Wed, Jul 28, 2021 at 9:33 PM Hongyi Zhao <hongyi.zhao@gmail.com>
> >>>> wrote:
> >>>>> On Wed, Jul 28, 2021 at 9:23 PM Thibaut Verron
> >>>>> <thibaut.verron@gmail.com> wrote:
> >>>>>> On 28/07/2021 15:03, Hongyi Zhao wrote:
> >>>>>>> On Wed, Jul 28, 2021 at 6:04 PM Jean-Christophe Helary
> >>>>>>> <lists@traduction-libre.org> wrote:
> >>>>>>>>> On Jul 28, 2021, at 18:54, Thibaut Verron
> >>>>>>>>> <thibaut.verron@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> On 28/07/2021 11:46, Hongyi Zhao wrote:
> >>>>>>>>>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron
> >>>>>>>>>> <thibaut.verron@gmail.com> wrote:
> >>>>>>>>>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
> >>>>>>>>>>>> When I start Emacs, I always notice the following message
> >>>>>>>>>>>> in *Messages* buffer:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Package cl is deprecated
> >>>>>>>>>>>>
> >>>>>>>>>>>> Any hints for eliminating it?
> >>>>>>>>>>> If you have (require 'cl) somewhere in your init file,
> >>>>>>>>>>> replace it with
> >>>>>>>>>>> (require 'cl-lib). You might need to change some macro calls
> >>>>>>>>>>> to use
> >>>>>>>>>>> cl-<name> instead of <name>.
> >>>>>>>>>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
> >>>>>>>>>> (require 'cl-lib)
> >>>>>>>>> Then it's from a package and you need to identify it.
> >>>>>>>>>
> >>>>>>>>> You can try (untested):
> >>>>>>>>>
> >>>>>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
> >>>>>>>> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
> >>>>>>>> -print
> >>>>>>> There are so many matches:
> >>>>>>>
> >>>>>>> $ find .emacs.d/ -name "*.el" -exec grep -q "(require 'cl)" {} \;
> >>>>>>> -print 2>/dev/null | sort -u | wc -l
> >>>>>>> 40
> >>>>>>>
> >>>>>>> So this method is basically useless for finding the problem.
> >>>>>> I just tried it, indeed quite a few packages contain some form of
> >>>>>> (require 'cl) as a backward-compatibility tool (52 matches in my
> >>>>>> case).
> >>>>>> Most of those are test files which are never loaded in a normal
> >>>>>> emacs
> >>>>>> session.
> >>>>>>
> >>>>>> To narrow the search, you can use egrep -q "^\(require 'cl\)"
> >>>>>> instead.
> >>>>>> In my .emacs, the matches go from 52 to 15. Interestingly enough,
> >>>>>> exactly one of them is loaded at init time (key-combo.el),
> >>>>>> without any
> >>>>>> warning.
> >>>>> Strange, I found nothing with this enhanced pattern:
> >>>>>
> >>>>> $ find .emacs.d/ -type f -name "*.el" -exec grep -q "^[ ]*\([
> >>>>> ]*require[ ]+'cl[ ]*\)" {} \; -print | wc -l
> >>>>> 0
> >>>> Sorry, egrep should be used:
> >>>>
> >>>> $ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^[ ]*\([
> >>>> ]*require[ ]+'cl[ ]*\)" {} \; -print | egrep -v '[/]tests?[/]'
> >>>> .emacs.d/straight/repos/dash.el/dash.el
> >>>> .emacs.d/straight/repos/dash.el/dev/examples.el
> >>>> .emacs.d/straight/repos/stardiviner-sdcv.el/sdcv.el
> >>>> .emacs.d/straight/repos/showtip/showtip.el
> >>>> .emacs.d/straight/repos/unicode-escape.el/unicode-escape.el
> >>>> .emacs.d/straight/repos/use-package/use-package-tests.el
> >>>> .emacs.d/straight/repos/macrostep/lib/cl-lib.el
> >>>> .emacs.d/straight/repos/macrostep/lib/ert.el
> >>>> .emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el
> >>>> .emacs.d/straight/repos/s.el/dev/ert.el
> >>> The point of the regexp was to exclude files which have something
> >>> (including indentation) before the form, if you allow [ ]* you lose
> >>> that. That's the case in dash.el for example.
> >>>
> >>> In any case, the number of candidates is now small enough that you can
> >>> examine them. The dev/ and lib/ folders can probably be safely
> >>> ignored to.
> >> If so, nothing seems responsible for the problem:
> >>
> >> $ find .emacs.d/ -type f -name "*.el" -exec egrep -q "^\(require
> >> 'cl\)" {} \; -print |egrep -v  '[/]tests?[/]'
> >> .emacs.d/straight/repos/use-package/use-package-tests.el
> >> .emacs.d/straight/repos/macrostep/lib/cl-lib.el
> >> .emacs.d/straight/repos/emacs-websocket/websocket-functional-test.el
> >
> > Then I guess you will have to check the other candidates, sorry. I'd
> > start with the 10 you found above, and then move to the other 30 if
> > necessary.
>
> showtip.el is one.

I've changed the corresponding lines into the following:

(eval-when-compile
  (require 'cl-lib))

But Emacs still reports the same messages, so there must be other culprits.

Hongyi
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> Then it's from a package and you need to identify it.

To be clear about one point -

You don't _need_ to identify it or change it.  You can
likely do so without creating problems, if you want to.

Deprecation does not mean desupport.  Library `cl.el' is
still _supported_.  At some future point it might become
desupported (probably will) - but it's supported now.

In addition, if you find (require 'cl) in some 3rd-party
library that you use, what do you intend to do about that?

You can notify the library maintainers, so they can decide
what to do or inform you about what you might do.  Or you
can modify that library source code yourself, to replace
that with (require 'cl-lib).

But besides not _needing_ to do any such thing, be aware
that a 3rd-party library may use such code intentionally,
for backward compatibility (even if you don't need that,
the library might want it, for other users on older Emacs
versions).

So if it's about a 3rd-party library, you might want to
check with its maintainers.

If it's a (require 'cl) in vanilla Emacs code then you
can file a bug report / enhancement request, to let the
Emacs maintainers know about it: `M-x report-emacs-bug'.

In any case, if you report it to whomever its maintainers
are, even if it gets "fixed" right away, unless you use
the most recent source code available (e.g. build Emacs
yourself, if the fix is in Emacs itself), you'll need to
wait some.

Remember, this is a byte-compiler warning message.  It's
not an error message.  There's really nothing that you
_need_ to fix.  But if the warning really bothers you then...

Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 10:21 PM Leo Butler <leo.butler@umanitoba.ca> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > On Wed, Jul 28, 2021 at 9:58 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >>
> >> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> >> > Date: Wed, 28 Jul 2021 21:41:03 +0800
> >> > Cc: Jean-Christophe Helary <lists@traduction-libre.org>,
> >> >  help-gnu-emacs <help-gnu-emacs@gnu.org>,
> >> >  Thibaut Verron <thibaut.verron@gmail.com>
> >> >
> >> > > (debug-on-message "Package cl is deprecated")
> >> >
> >> > I tried this method, but meet the following warning:
> >> >
> >> > Warning (initialization): An error occurred while loading
> >> > ‘/home/werner/.emacs.d/init.el’:
> >> >
> >> > Symbol's function definition is void: debug-on-message
> >>
> >> debug-on-message is a variable, not a function.
> >
> > Then, how to pinpoint the target message?
>
> Ahem. I should have written
>
> (setq debug-on-message "Package cl is deprecated")

With the above line at the top of my ~/.emacs.d/init.el, Emacs reports
the following:

Debugger entered--Lisp error: "Package cl is deprecated"
  message("%s" "Package cl is deprecated")
  #f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)("Package
cl is deprecated")
  apply(#f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)
"Package cl is deprecated")
  timer-event-handler([t 0 0 0 nil #f(compiled-function (msg)
#<bytecode -0xb147a2018986fae>) ("Package cl is deprecated") idle 0])

It seems to me that the source el file in question does not correspond
quite so intuitively to the above messages.

> Ref.
>
> (info "elisp")
> (Info-index "debug-on-message")
>
> > Where is my mistake?
>
> As Eli noted, emacs must be in *info* looking at the elisp manual. My
> mistake.

Thank you, the following does the trick:

`C-h i M-: (info "elisp") RET M-: (Info-index "debug-on-message") RET':

-- Variable: debug-on-message
     If you set ‘debug-on-message’ to a regular expression, Emacs will
     enter the debugger if it displays a matching message in the echo
     area.  For example, this can be useful when trying to find the
     cause of a particular message.

But how to evaluate the above command more concisely?

> Anyhow, debug-on-message will help you isolate the source of the
> problem. You may need to play with the regexp ("Package ..."), though.

Thank you for your suggestion.

Hongyi

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Wed, Jul 28, 2021 at 10:36 PM Drew Adams <drew.adams@oracle.com> wrote:
>
> > Then it's from a package and you need to identify it.
>
> To be clear about one point -
>
> You don't _need_ to identify it or change it.  You can
> likely do so without creating problems, if you want to.
>
> Deprecation does not mean desupport.  Library `cl.el' is
> still _supported_.  At some future point it might become
> desupported (probably will) - but it's supported now.
>
> In addition, if you find (require 'cl) in some 3rd-party
> library that you use, what do you intend to do about that?
>
> You can notify the library maintainers, so they can decide
> what to do or inform you about what you might do.  Or you
> can modify that library source code yourself, to replace
> that with (require 'cl-lib).
>
> But besides not _needing_ to do any such thing, be aware
> that a 3rd-party library may use such code intentionally,
> for backward compatibility (even if you don't need that,
> the library might want it, for other users on older Emacs
> versions).
>
> So if it's about a 3rd-party library, you might want to
> check with its maintainers.
>
> If it's a (require 'cl) in vanilla Emacs code then you
> can file a bug report / enhancement request, to let the
> Emacs maintainers know about it: `M-x report-emacs-bug'.
>
> In any case, if you report it to whomever its maintainers
> are, even if it gets "fixed" right away, unless you use
> the most recent source code available (e.g. build Emacs
> yourself, if the fix is in Emacs itself), you'll need to
> wait some.
>
> Remember, this is a byte-compiler warning message.  It's
> not an error message.  There's really nothing that you
> _need_ to fix.  But if the warning really bothers you then...

Got it. Thank you for your explanation and systematic comments.

Regards,
Hongyi

Re: Package cl is deprecated

[Marcin Borkowski]

On 2021-07-28, at 11:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:

> On 28/07/2021 11:46, Hongyi Zhao wrote:
>> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
>>> On 28/07/2021 11:23, Hongyi Zhao wrote:
>>>> When I start Emacs, I always notice the following message in *Messages* buffer:
>>>>
>>>> Package cl is deprecated
>>>>
>>>> Any hints for eliminating it?
>>> If you have (require 'cl) somewhere in your init file, replace it with
>>> (require 'cl-lib). You might need to change some macro calls to use
>>> cl-<name> instead of <name>.
>> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
>> (require 'cl-lib)
>
> Then it's from a package and you need to identify it.
>
> You can try (untested):
>
> find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
>
> But I'm sure there is an easier way to do it from within emacs.

You might be interested in this:
https://github.com/Malabarba/elisp-bug-hunter

Hth,

-- 
Marcin Borkowski
http://mbork.pl

Re: Package cl is deprecated

[Eli Zaretskii]

> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Wed, 28 Jul 2021 22:48:33 +0800
> Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs <help-gnu-emacs@gnu.org>
> 
> > (setq debug-on-message "Package cl is deprecated")
> 
> With the above line at the top of my ~/.emacs.d/init.el, Emacs reports
> the following:
> 
> Debugger entered--Lisp error: "Package cl is deprecated"
>   message("%s" "Package cl is deprecated")
>   #f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)("Package
> cl is deprecated")
>   apply(#f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)
> "Package cl is deprecated")
>   timer-event-handler([t 0 0 0 nil #f(compiled-function (msg)
> #<bytecode -0xb147a2018986fae>) ("Package cl is deprecated") idle 0])

What does the following display?

  M-x list-timers RET

Re: Package cl is deprecated

[Eli Zaretskii]

> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Wed, 28 Jul 2021 22:48:33 +0800
> Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs <help-gnu-emacs@gnu.org>
> 
> > (setq debug-on-message "Package cl is deprecated")
> 
> With the above line at the top of my ~/.emacs.d/init.el, Emacs reports
> the following:
> 
> Debugger entered--Lisp error: "Package cl is deprecated"
>   message("%s" "Package cl is deprecated")
>   #f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)("Package
> cl is deprecated")
>   apply(#f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)
> "Package cl is deprecated")
>   timer-event-handler([t 0 0 0 nil #f(compiled-function (msg)
> #<bytecode -0xb147a2018986fae>) ("Package cl is deprecated") idle 0])
> 
> It seems to me that the source el file in question does not correspond
> quite so intuitively to the above messages.

In addition to what I just asked, try adding the following to the top
of your ~/.emacs.d/init.el:

  (setq force-load-messages t)

Then look in *Messages* for

  Loading 'cl'...

And the previous "Loading..." line will hopefully tell you what was
the package whose load caused Emacs to load cl.

Re: Package cl is deprecated

[Hongyi Zhao]

On Thu, Jul 29, 2021 at 2:28 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> > Date: Wed, 28 Jul 2021 22:48:33 +0800
> > Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs <help-gnu-emacs@gnu.org>
> >
> > > (setq debug-on-message "Package cl is deprecated")
> >
> > With the above line at the top of my ~/.emacs.d/init.el, Emacs reports
> > the following:
> >
> > Debugger entered--Lisp error: "Package cl is deprecated"
> >   message("%s" "Package cl is deprecated")
> >   #f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)("Package
> > cl is deprecated")
> >   apply(#f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)
> > "Package cl is deprecated")
> >   timer-event-handler([t 0 0 0 nil #f(compiled-function (msg)
> > #<bytecode -0xb147a2018986fae>) ("Package cl is deprecated") idle 0])
>
> What does the following display?
>
>   M-x list-timers RET

M-x list-timers RET SPC

               1.5s         5.0s auto-revert-buffers
           4m 30.5s      5m 0.0s recentf-save-list
   *           0.0s            t show-paren-function
   *           0.5s            t #f(compiled-function () #<bytecode
0x12c5e9b0cd01ea9e> [jit-lock--antiblink-grace-timer
jit-lock-context-fontify])
   *           0.5s            t posframe-hidehandler-daemon-function
   *           1.0s            t which-key--update

Hongyi
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Hongyi Zhao]

On Thu, Jul 29, 2021 at 2:32 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> > Date: Wed, 28 Jul 2021 22:48:33 +0800
> > Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs <help-gnu-emacs@gnu.org>
> >
> > > (setq debug-on-message "Package cl is deprecated")
> >
> > With the above line at the top of my ~/.emacs.d/init.el, Emacs reports
> > the following:
> >
> > Debugger entered--Lisp error: "Package cl is deprecated"
> >   message("%s" "Package cl is deprecated")
> >   #f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)("Package
> > cl is deprecated")
> >   apply(#f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)
> > "Package cl is deprecated")
> >   timer-event-handler([t 0 0 0 nil #f(compiled-function (msg)
> > #<bytecode -0xb147a2018986fae>) ("Package cl is deprecated") idle 0])
> >
> > It seems to me that the source el file in question does not correspond
> > quite so intuitively to the above messages.
>
> In addition to what I just asked, try adding the following to the top
> of your ~/.emacs.d/init.el:
>
>   (setq force-load-messages t)

I tried with the following lines added at the very beginning of
`~/.emacs.d/init.el':

(setq force-load-messages t)
(setq debug-on-message "Package cl is deprecated")

> Then look in *Messages* for
>
>   Loading 'cl'...

I can't find the above line in *Messages*, here is the code snippet at
the bottom in *Messages* when Emacs paused during initialization:

.emacs.d/straight/build/counsel-edit-mode/counsel-edit-mode.el:
Warning: Use keywords rather than deprecated positional arguments to
`define-minor-mode' [2 times]
Loading /home/werner/.emacs.d/straight/build/counsel-edit-mode/counsel-edit-mode.el
(source)...done
Loading which-key...done
Loading company-dabbrev...done
Loading company-keywords...done
Loading company-files...done
Loading company-ispell...
Loading ispell...done
Loading company-ispell...done
Loading flyspell...done
Wrote /home/werner/.emacs.d/recentf
Starting new Ispell process /usr/bin/aspell with default dictionary...done
Error enabling Flyspell mode:
(No Ispell process to read output from!)
For information about GNU Emacs and the GNU system, type C-h C-a.
Package cl is deprecated
Loading debug...done
Entering debugger...
Loading cl-print...done
End of buffer [6 times]
Wrote /home/werner/.emacs.d/recentf


> And the previous "Loading..." line will hopefully tell you what was
> the package whose load caused Emacs to load cl.

Hongyi
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Hongyi Zhao]

On Thu, Jul 29, 2021 at 2:11 AM Marcin Borkowski <mbork@mbork.pl> wrote:
>
>
> On 2021-07-28, at 11:54, Thibaut Verron <thibaut.verron@gmail.com> wrote:
>
> > On 28/07/2021 11:46, Hongyi Zhao wrote:
> >> On Wed, Jul 28, 2021 at 5:33 PM Thibaut Verron <thibaut.verron@gmail.com> wrote:
> >>> On 28/07/2021 11:23, Hongyi Zhao wrote:
> >>>> When I start Emacs, I always notice the following message in *Messages* buffer:
> >>>>
> >>>> Package cl is deprecated
> >>>>
> >>>> Any hints for eliminating it?
> >>> If you have (require 'cl) somewhere in your init file, replace it with
> >>> (require 'cl-lib). You might need to change some macro calls to use
> >>> cl-<name> instead of <name>.
> >> $ egrep 'require[ ]*'\''cl' .emacs.d/init.el
> >> (require 'cl-lib)
> >
> > Then it's from a package and you need to identify it.
> >
> > You can try (untested):
> >
> > find .emacs.d/ -name "*.el" -exec grep "(require 'cl)" {} \;
> >
> > But I'm sure there is an easier way to do it from within emacs.
>
> You might be interested in this:
> https://github.com/Malabarba/elisp-bug-hunter

I tried with it, but it failed to hunt any errors out, except that it
will also get the same results given by the following codes in the
very beginning of the `~/.emacs.d/init.el' file:

(setq force-load-messages t)
(setq debug-on-message "Package cl is deprecated")

Hongyi
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: Package cl is deprecated

[Eli Zaretskii]

> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Thu, 29 Jul 2021 10:27:09 +0800
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> 
> >   (setq force-load-messages t)
> 
> I tried with the following lines added at the very beginning of
> `~/.emacs.d/init.el':
> 
> (setq force-load-messages t)
> (setq debug-on-message "Package cl is deprecated")

No, please try only with the first one, and lose the second one.  The
second one prevents us from seeing the culprit, because it stops the
loading process in its tracks.

Re: Package cl is deprecated

[Eli Zaretskii]

> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Thu, 29 Jul 2021 10:18:33 +0800
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> 
> M-x list-timers RET SPC
> 
>                1.5s         5.0s auto-revert-buffers
>            4m 30.5s      5m 0.0s recentf-save-list
>    *           0.0s            t show-paren-function
>    *           0.5s            t #f(compiled-function () #<bytecode
> 0x12c5e9b0cd01ea9e> [jit-lock--antiblink-grace-timer
> jit-lock-context-fontify])
>    *           0.5s            t posframe-hidehandler-daemon-function
>    *           1.0s            t which-key--update

The last two could be the evidence, so I'd look at posframe and
which-key.  If you remove them from the load, does the problem
persist?

Re: Package cl is deprecated

[Hongyi Zhao]

On Thu, Jul 29, 2021 at 2:18 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> > Date: Thu, 29 Jul 2021 10:18:33 +0800
> > Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> >
> > M-x list-timers RET SPC
> >
> >                1.5s         5.0s auto-revert-buffers
> >            4m 30.5s      5m 0.0s recentf-save-list
> >    *           0.0s            t show-paren-function
> >    *           0.5s            t #f(compiled-function () #<bytecode
> > 0x12c5e9b0cd01ea9e> [jit-lock--antiblink-grace-timer
> > jit-lock-context-fontify])
> >    *           0.5s            t posframe-hidehandler-daemon-function
> >    *           1.0s            t which-key--update
>
> The last two could be the evidence, so I'd look at posframe and
> which-key.  If you remove them from the load, does the problem
> persist?

I commented out the corresponding configurations to the above two
packages in `~/.emacs.d/init.el', and put the following lines at the
very beginning of it:

(setq force-load-messages t)
(put 'list-timers 'disabled nil)

The messages "Package cl is deprecated" still appear during Emacs
startup. Then I run the command `M-x list-timers RET', and obtain the
following results:

               0.3s            - undo-auto--boundary-timer
               1.8s         5.0s auto-revert-buffers
           4m 51.8s      5m 0.0s recentf-save-list
   *           0.0s            t show-paren-function
   *           0.5s            t #f(compiled-function () #<bytecode
0x12c7da80444ad69e> [jit-lock--antiblink-grace-timer
jit-lock-context-fontify])
   *           0.5s      :repeat blink-cursor-start

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > In addition to what I just asked, try adding the 
> > following to the top of your ~/.emacs.d/init.el:
> >   (setq force-load-messages t)
> 
> > Then look in *Messages* for
> >   Loading 'cl'...
> 
> I can't find the above line in *Messages*...

You can also try `C-h v load-history'.

Or type `load-history' in *scratch* (without the
quotes), put your cursor after that text, and use
`M-x pp-eval-last-sexp'.

Each of those shows you your complete history of
loading Elisp files.

Search the *Help* buffer (for `C-h v') or search
the *Pp Eval Output* buffer (for `pp-...') for
loading of cl.el[c].  Just before that you'll see
other loads - those can give you a hint of what
caused cl.el[c] to be loaded.

Re: [External] : Re: Package cl is deprecated

[Arthur Miller]

[-- Attachment #1: Type: text/plain, Size: 2367 bytes --]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> On Wed, Jul 28, 2021 at 10:36 PM Drew Adams <drew.adams@oracle.com> wrote:
>>
>> > Then it's from a package and you need to identify it.
>>
>> To be clear about one point -
>>
>> You don't _need_ to identify it or change it.  You can
>> likely do so without creating problems, if you want to.
>>
>> Deprecation does not mean desupport.  Library `cl.el' is
>> still _supported_.  At some future point it might become
>> desupported (probably will) - but it's supported now.
>>
>> In addition, if you find (require 'cl) in some 3rd-party
>> library that you use, what do you intend to do about that?
>>
>> You can notify the library maintainers, so they can decide
>> what to do or inform you about what you might do.  Or you
>> can modify that library source code yourself, to replace
>> that with (require 'cl-lib).
>>
>> But besides not _needing_ to do any such thing, be aware
>> that a 3rd-party library may use such code intentionally,
>> for backward compatibility (even if you don't need that,
>> the library might want it, for other users on older Emacs
>> versions).
>>
>> So if it's about a 3rd-party library, you might want to
>> check with its maintainers.
>>
>> If it's a (require 'cl) in vanilla Emacs code then you
>> can file a bug report / enhancement request, to let the
>> Emacs maintainers know about it: `M-x report-emacs-bug'.
>>
>> In any case, if you report it to whomever its maintainers
>> are, even if it gets "fixed" right away, unless you use
>> the most recent source code available (e.g. build Emacs
>> yourself, if the fix is in Emacs itself), you'll need to
>> wait some.
>>
>> Remember, this is a byte-compiler warning message.  It's
>> not an error message.  There's really nothing that you
>> _need_ to fix.  But if the warning really bothers you then...
>
> Got it. Thank you for your explanation and systematic comments.
>
> Regards,
> Hongyi

By now you have got so many good explanations and tips. Here is one
curiosa, if you have Helm and Ag (silversearcher) installed, then you
can do grep search in your elpa catalogue and get nice visual list of
which packages haven't updated their require statements (and probably
cl- prefix too). This is a screenhot from my Emacs, and as I see even
some packages updated as late as in 2021 does still come with old
require 'cl statements.


[-- Attachment #2: require-cl.png --]
[-- Type: image/png, Size: 451540 bytes --]

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

[-- Attachment #1: Type: text/plain, Size: 3172 bytes --]

On Thu, Jul 29, 2021 at 11:26 PM Arthur Miller <arthur.miller@live.com> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > On Wed, Jul 28, 2021 at 10:36 PM Drew Adams <drew.adams@oracle.com> wrote:
> >>
> >> > Then it's from a package and you need to identify it.
> >>
> >> To be clear about one point -
> >>
> >> You don't _need_ to identify it or change it.  You can
> >> likely do so without creating problems, if you want to.
> >>
> >> Deprecation does not mean desupport.  Library `cl.el' is
> >> still _supported_.  At some future point it might become
> >> desupported (probably will) - but it's supported now.
> >>
> >> In addition, if you find (require 'cl) in some 3rd-party
> >> library that you use, what do you intend to do about that?
> >>
> >> You can notify the library maintainers, so they can decide
> >> what to do or inform you about what you might do.  Or you
> >> can modify that library source code yourself, to replace
> >> that with (require 'cl-lib).
> >>
> >> But besides not _needing_ to do any such thing, be aware
> >> that a 3rd-party library may use such code intentionally,
> >> for backward compatibility (even if you don't need that,
> >> the library might want it, for other users on older Emacs
> >> versions).
> >>
> >> So if it's about a 3rd-party library, you might want to
> >> check with its maintainers.
> >>
> >> If it's a (require 'cl) in vanilla Emacs code then you
> >> can file a bug report / enhancement request, to let the
> >> Emacs maintainers know about it: `M-x report-emacs-bug'.
> >>
> >> In any case, if you report it to whomever its maintainers
> >> are, even if it gets "fixed" right away, unless you use
> >> the most recent source code available (e.g. build Emacs
> >> yourself, if the fix is in Emacs itself), you'll need to
> >> wait some.
> >>
> >> Remember, this is a byte-compiler warning message.  It's
> >> not an error message.  There's really nothing that you
> >> _need_ to fix.  But if the warning really bothers you then...
> >
> > Got it. Thank you for your explanation and systematic comments.
> >
> > Regards,
> > Hongyi
>
> By now you have got so many good explanations and tips. Here is one
> curiosa, if you have Helm and Ag (silversearcher) installed, then you
> can do grep search in your elpa catalogue

In my situation, I use straight [1] as the package manager, so the
corresponding catalog is located at `~/.emacs.d/straight/repos/'.

> and get nice visual list of
> which packages haven't updated their require statements (and probably
> cl- prefix too). This is a screenhot from my Emacs, and as I see even
> some packages updated as late as in 2021 does still come with old
> require 'cl statements.

Based on your above notes, I tried with helm-ag [2], and with the
pattern `(require 'cl)', 38 candidates are retrieved. See the
attachment for more detailed info.


[1] https://github.com/raxod502/straight.el
[2] https://github.com/emacsorphanage/helm-ag


-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

[-- Attachment #2: Selection_005.png --]
[-- Type: image/png, Size: 231056 bytes --]

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

On Thu, Jul 29, 2021 at 10:26 PM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > In addition to what I just asked, try adding the
> > > following to the top of your ~/.emacs.d/init.el:
> > >   (setq force-load-messages t)
> >
> > > Then look in *Messages* for
> > >   Loading 'cl'...
> >
> > I can't find the above line in *Messages*...
>
> You can also try `C-h v load-history'.
>
> Or type `load-history' in *scratch* (without the
> quotes), put your cursor after that text, and use
> `M-x pp-eval-last-sexp'.
>
> Each of those shows you your complete history of
> loading Elisp files.
>
> Search the *Help* buffer (for `C-h v') or search
> the *Pp Eval Output* buffer (for `pp-...') for
> loading of cl.el[c].  Just before that you'll see
> other loads - those can give you a hint of what
> caused cl.el[c] to be loaded.

Thank you very much for letting me know so many wonderful tricks. I
tried with swiper to search the *Pp Eval Output* buffer, but nothing
matched, as shown in the attachment. Did I do something wrong?

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

[-- Attachment #2: Selection_007.png --]
[-- Type: image/png, Size: 178783 bytes --]

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > You can also try `C-h v load-history'.
> >
> > Or type `load-history' in *scratch* (without the
> > quotes), put your cursor after that text, and use
> > `M-x pp-eval-last-sexp'.
> >
> > Each of those shows you your complete history of
> > loading Elisp files.
> >
> > Search the *Help* buffer (for `C-h v') or search
> > the *Pp Eval Output* buffer (for `pp-...') for
> > loading of cl.el[c].  Just before that you'll see
> > other loads - those can give you a hint of what
> > caused cl.el[c] to be loaded.
> 
> Thank you very much for letting me know so many wonderful tricks. I
> tried with swiper to search the *Pp Eval Output* buffer, but nothing
> matched, as shown in the attachment. Did I do something wrong?

Try just Isearch.  Search for `(require . cl)' (note the dot).

If you have a library `foo.el' in directory
`/some/dir/somewhere/', where `foo.el' requires
library cl then you'll find a sexp such as this:

 ("/some/dir/somewhere/foo.el"
  ...
  (require . cl)
  ...)

You may well have loaded multiple libraries that
require cl.  You may be interested in all of them,
but the first one is likely the one that loaded
cl.el[c].

(Searching `C-h v load-history' in *Help* is
harder, because it may split `(require 'cl)' across
two lines.)

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Fri, Jul 30, 2021 at 12:03 PM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > You can also try `C-h v load-history'.
> > >
> > > Or type `load-history' in *scratch* (without the
> > > quotes), put your cursor after that text, and use
> > > `M-x pp-eval-last-sexp'.
> > >
> > > Each of those shows you your complete history of
> > > loading Elisp files.
> > >
> > > Search the *Help* buffer (for `C-h v') or search
> > > the *Pp Eval Output* buffer (for `pp-...') for
> > > loading of cl.el[c].  Just before that you'll see
> > > other loads - those can give you a hint of what
> > > caused cl.el[c] to be loaded.
> >
> > Thank you very much for letting me know so many wonderful tricks. I
> > tried with swiper to search the *Pp Eval Output* buffer, but nothing
> > matched, as shown in the attachment. Did I do something wrong?
>
> Try just Isearch.  Search for `(require . cl)' (note the dot).

Do you mean:

`M-x isearch-forward RET (require . cl) RET'?

I tried the above command under `.emacs.d/straight/repos' directory,
but it doesn't give any results.

> If you have a library `foo.el' in directory
> `/some/dir/somewhere/', where `foo.el' requires
> library cl then you'll find a sexp such as this:
>
>  ("/some/dir/somewhere/foo.el"
>   ...
>   (require . cl)
>   ...)
>
> You may well have loaded multiple libraries that
> require cl.  You may be interested in all of them,
> but the first one is likely the one that loaded
> cl.el[c].
>
> (Searching `C-h v load-history' in *Help* is
> harder, because it may split `(require 'cl)' across
> two lines.)

If so, the spanning line pattern should do the trick. Am I right?

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > Try just Isearch.  Search for `(require . cl)' (note the dot).
> 
> Do you mean: `M-x isearch-forward RET (require . cl) RET'?

`C-s (require . cl)'

> I tried the above command under `.emacs.d/straight/repos' directory,
> but it doesn't give any results.

If cl.el[c] was loaded, then I'd expect that fact
to be recorded in `load-history'.  Why you're not
finding it there, I don't know.  If it's in fact
not there then I don't know why that's the case
either.

> > If you have a library `foo.el' in directory
> > `/some/dir/somewhere/', where `foo.el' requires
> > library cl then you'll find a sexp such as this:
> >
> >  ("/some/dir/somewhere/foo.el"
> >   ...
> >   (require . cl)
> >   ...)
> >
> > You may well have loaded multiple libraries that
> > require cl.  You may be interested in all of them,
> > but the first one is likely the one that loaded
> > cl.el[c].
> >
> > (Searching `C-h v load-history' in *Help* is
> > harder, because it may split `(require 'cl)' across
> > two lines.)
> 
> If so, the spanning line pattern should do the trick. Am I right?

Yes. `C-M-s' for this in *Help* for `C-h v load-history'.

(require[
 ]+[.][
 ]+cl)

Re: Package cl is deprecated

[Stefan Monnier via Users list for the GNU Emacs text editor]

> Debugger entered--Lisp error: "Package cl is deprecated"
>   message("%s" "Package cl is deprecated")
>   #f(compiled-function (msg) #<bytecode -0xb147a2018986fae>)("Package cl is deprecated")
>   apply(#f(compiled-function (msg) #<bytecode -0xb147a2018986fae>) "Package cl is deprecated")
>   timer-event-handler([t 0 0 0 nil #f(compiled-function (msg) #<bytecode -0xb147a2018986fae>) ("Package cl is deprecated") idle 0])

Duh, indeed `do-after-load-evaluation` emits the warning via a timer
(to avoid the warning being hidden by a subsequent message during
startup).

You can hack around this with:

    (setq debug-on-message "Package cl is deprecated")
    (setq noninteractive t)

which should hopefully give you a more informative backtrace.

Sadly this `noninteractive` setting may have undesired side effects, so
buyer beware.  A comment in that function points out we should probably
use `display-warning` instead.


        Stefan

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]

On Fri, Jul 30, 2021 at 11:56 PM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > Try just Isearch.  Search for `(require . cl)' (note the dot).
> >
> > Do you mean: `M-x isearch-forward RET (require . cl) RET'?
>
> `C-s (require . cl)'

I tried again and it worked, as shown in the attachment.

> > I tried the above command under `.emacs.d/straight/repos' directory,
> > but it doesn't give any results.
>
> If cl.el[c] was loaded, then I'd expect that fact
> to be recorded in `load-history'.  Why you're not
> finding it there, I don't know.  If it's in fact
> not there then I don't know why that's the case
> either.
>
> > > If you have a library `foo.el' in directory
> > > `/some/dir/somewhere/', where `foo.el' requires
> > > library cl then you'll find a sexp such as this:
> > >
> > >  ("/some/dir/somewhere/foo.el"
> > >   ...
> > >   (require . cl)
> > >   ...)
> > >
> > > You may well have loaded multiple libraries that
> > > require cl.  You may be interested in all of them,
> > > but the first one is likely the one that loaded
> > > cl.el[c].
> > >
> > > (Searching `C-h v load-history' in *Help* is
> > > harder, because it may split `(require 'cl)' across
> > > two lines.)
> >
> > If so, the spanning line pattern should do the trick. Am I right?
>
> Yes. `C-M-s' for this in *Help* for `C-h v load-history'.
>
> (require[
>  ]+[.][
>  ]+cl)

Thank you for showing me this pattern. TBF, it seems to me that the
syntax of line spanning match pattern is very strange. It would be
nice if there were some explanation for how to build this pattern.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

[-- Attachment #2: Selection_004.png --]
[-- Type: image/png, Size: 154178 bytes --]

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sat, Jul 31, 2021 at 8:35 AM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
>
> On Fri, Jul 30, 2021 at 11:56 PM Drew Adams <drew.adams@oracle.com> wrote:
> >
> > > > Try just Isearch.  Search for `(require . cl)' (note the dot).
> > >
> > > Do you mean: `M-x isearch-forward RET (require . cl) RET'?
> >
> > `C-s (require . cl)'
>
> I tried again and it worked, as shown in the attachment.
>
> > > I tried the above command under `.emacs.d/straight/repos' directory,
> > > but it doesn't give any results.
> >
> > If cl.el[c] was loaded, then I'd expect that fact
> > to be recorded in `load-history'.  Why you're not
> > finding it there, I don't know.  If it's in fact
> > not there then I don't know why that's the case
> > either.
> >
> > > > If you have a library `foo.el' in directory
> > > > `/some/dir/somewhere/', where `foo.el' requires
> > > > library cl then you'll find a sexp such as this:
> > > >
> > > >  ("/some/dir/somewhere/foo.el"
> > > >   ...
> > > >   (require . cl)
> > > >   ...)
> > > >
> > > > You may well have loaded multiple libraries that
> > > > require cl.  You may be interested in all of them,
> > > > but the first one is likely the one that loaded
> > > > cl.el[c].
> > > >
> > > > (Searching `C-h v load-history' in *Help* is
> > > > harder, because it may split `(require 'cl)' across
> > > > two lines.)
> > >
> > > If so, the spanning line pattern should do the trick. Am I right?
> >
> > Yes. `C-M-s' for this in *Help* for `C-h v load-history'.
> >
> > (require[
> >  ]+[.][
> >  ]+cl)
>
> Thank you for showing me this pattern. TBF, it seems to me that the
> syntax of line spanning match pattern is very strange. It would be
> nice if there were some explanation for how to build this pattern.

To be more specifically, since this is a multiline match pattern, why
don't you any end-of-line metacharacter, i.e., `$' [1] in your above
pattern?

[1] https://www.emacswiki.org/emacs/RegularExpression

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Fri, Jul 30, 2021 at 11:56 PM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > Try just Isearch.  Search for `(require . cl)' (note the dot).
> >
> > Do you mean: `M-x isearch-forward RET (require . cl) RET'?
>
> `C-s (require . cl)'
>
> > I tried the above command under `.emacs.d/straight/repos' directory,
> > but it doesn't give any results.
>
> If cl.el[c] was loaded, then I'd expect that fact
> to be recorded in `load-history'.  Why you're not
> finding it there, I don't know.  If it's in fact
> not there then I don't know why that's the case
> either.
>
> > > If you have a library `foo.el' in directory
> > > `/some/dir/somewhere/', where `foo.el' requires
> > > library cl then you'll find a sexp such as this:
> > >
> > >  ("/some/dir/somewhere/foo.el"
> > >   ...
> > >   (require . cl)
> > >   ...)
> > >
> > > You may well have loaded multiple libraries that
> > > require cl.  You may be interested in all of them,
> > > but the first one is likely the one that loaded
> > > cl.el[c].
> > >
> > > (Searching `C-h v load-history' in *Help* is
> > > harder, because it may split `(require 'cl)' across
> > > two lines.)
> >
> > If so, the spanning line pattern should do the trick. Am I right?
>
> Yes. `C-M-s' for this in *Help* for `C-h v load-history'.

Based on the guidance here [1], I tried the following two commands:

 C-M-s                   incremental forward search matching regexp
 C-M-r                   incremental backward search matching regexp

And it seems that, by default, the `C-M-r' is bound to
isearch-backward-regexp, while `C-M-s' is not bound to
isearch-forward-regexp.

> (require[
>  ]+[.][
>  ]+cl)

[1] https://www.emacswiki.org/emacs/RegularExpression

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> > (require[
> >  ]+[.][
> >  ]+cl)
>
> Thank you for showing me this pattern. TBF, it seems to me that the
> syntax of line spanning match pattern is very strange. It would be
> nice if there were some explanation for how to build this pattern.

I suggest to use "xr" which is the reverse of `rx' which is a thing that
allows to construct regular expressions from a simple and well
documented symbolic description language (see doc of `rx').  So

(xr "(require[
 ]+[.][
 ]+cl)")

==>
 (seq "(require"
      (one-or-more (any "\n "))
      "."
      (one-or-more (any "\n "))
      "cl)")

As mentioned, see the help of `rx' to see what any part means, though
it's already quite readable.

Note that for regexp searching there is no Lisp interpreter involved
that would read your input string.  What you type is used directly,
which means that \n does not match a newline (but instead the character
"n").  That's why the search pattern includes real newlines.  This is
bit confusing at the beginning, anyway, that's already all, you can do
it ;-)


Michael.

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sat, Jul 31, 2021 at 9:34 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > > (require[
> > >  ]+[.][
> > >  ]+cl)
> >
> > Thank you for showing me this pattern. TBF, it seems to me that the
> > syntax of line spanning match pattern is very strange. It would be
> > nice if there were some explanation for how to build this pattern.
>
> I suggest to use "xr" which is the reverse of `rx' which is a thing that
> allows to construct regular expressions from a simple and well
> documented symbolic description language (see doc of `rx').  So
>
> (xr "(require[
>  ]+[.][
>  ]+cl)")

I failed to expand the above lisp code snippet with macrostep [1]:

`M-x macrostep-expand RET':
macrostep-sexp-bounds: (xr ...) is not a macro form

Further, I tried with `C-h o ^xr$', and nothing is matched.

> ==>
>  (seq "(require"
>       (one-or-more (any "\n "))
>       "."
>       (one-or-more (any "\n "))
>       "cl)")
>
> As mentioned, see the help of `rx' to see what any part means, though
> it's already quite readable.
>
> Note that for regexp searching there is no Lisp interpreter involved
> that would read your input string.  What you type is used directly,
> which means that \n does not match a newline (but instead the character
> "n").  That's why the search pattern includes real newlines.  This is
> bit confusing at the beginning, anyway, that's already all, you can do
> it ;-)
>
>
> Michael.

[1] https://github.com/joddie/macrostep

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> Further, I tried with `C-h o ^xr$', and nothing is matched.

You just need to install the "xr" package from Gnu Elpa.  This provides
the `xr' function (it's not a macro).

Michael.

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sat, Jul 31, 2021 at 12:39 PM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > Further, I tried with `C-h o ^xr$', and nothing is matched.
>
> You just need to install the "xr" package from Gnu Elpa.  This provides
> the `xr' function (it's not a macro).

Thank you again. I installed this package with the following command:

(use-package xr)

Then I put the following code into scratch buffer:

(xr "(require[
 ]+[.][
 ]+cl)")

Run `C-j' on the above code snippet with the point at the end of it, I
obtain the following which you have shown previously:

(seq "(require" (one-or-more (any "
 ")) "." (one-or-more (any "
 ")) "cl)")


Best regards,
Hongyi

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sat, Jul 31, 2021 at 9:34 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > > (require[
> > >  ]+[.][
> > >  ]+cl)
> >
> > Thank you for showing me this pattern. TBF, it seems to me that the
> > syntax of line spanning match pattern is very strange. It would be
> > nice if there were some explanation for how to build this pattern.
>
> I suggest to use "xr" which is the reverse of `rx' which is a thing that
> allows to construct regular expressions from a simple and well
> documented symbolic description language (see doc of `rx').  So
>
> (xr "(require[
>  ]+[.][
>  ]+cl)")
>
> ==>
>  (seq "(require"
>       (one-or-more (any "\n "))
>       "."
>       (one-or-more (any "\n "))
>       "cl)")
>
> As mentioned, see the help of `rx' to see what any part means, though
> it's already quite readable.
>
> Note that for regexp searching there is no Lisp interpreter involved
> that would read your input string.  What you type is used directly,
> which means that \n does not match a newline (but instead the character
> "n").  That's why the search pattern includes real newlines.  This is
> bit confusing at the beginning, anyway, that's already all, you can do
> it ;-)

For someone who knows it for the first time, like me, it’s really
strange. Anyway, thank you and all the others here for letting me know
so many treasures related to the Emacs ecosystem.

Regards,
Hongyi

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > `C-s (require . cl)'
> 
> I tried again and it worked, as shown in the attachment.
>

> > Yes. `C-M-s' for this in *Help* for `C-h v load-history'.
> >
> > (require[
> >  ]+[.][
> >  ]+cl)
> 
> Thank you for showing me this pattern. TBF, it seems to me that the
> syntax of line spanning match pattern is very strange. It would be
> nice if there were some explanation for how to build this pattern.

See the Emacs manual, node `Lax Search'.  Depending on your
value of option `search-whitespace-regexp' you can just
type a space char to match one or more whitespace chars,
including newline chars.  I you set it to "[ 	

]+" (which corresponds to "[ \t\r\n]+" then you can just
search with `C-s' for `(require . cl)'.  That will cross
newlines.

https://www.gnu.org/software/emacs/manual/html_node/emacs/Lax-Search.html

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> Based on the guidance here [1], I tried the following two commands:
> 
>  C-M-s                   incremental forward search matching regexp
>  C-M-r                   incremental backward search matching regexp
> 
> And it seems that, by default, the `C-M-r' is bound to
> isearch-backward-regexp, while `C-M-s' is not bound to
> isearch-forward-regexp.

Start Emacs with `emacs -Q' (no init file), and I think
`C-h k C-M-s' will tell you:

  C-M-s runs the command isearch-forward-regexp

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > Thank you for showing me this pattern. TBF, it seems to me that the
> > syntax of line spanning match pattern is very strange. It would be
> > nice if there were some explanation for how to build this pattern.
> 
> To be more specifically, since this is a multiline match pattern, why
> don't you any end-of-line metacharacter, i.e., `$' [1] in your above
> pattern?

There's no reason to match end-of-line.
But you can match newline chars.

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Drew Adams <drew.adams@oracle.com> writes:

> > [...] why don't you any end-of-line metacharacter, i.e., `$' [1] in
> > your above pattern?
>
> There's no reason to match end-of-line.
> But you can match newline chars.

With other words: "$" _doesn't_ match a newline character, it just
matches the position (the empty string) at a line's end.  If you want to
have matches spanning lines, you must match newline characters in some
way.

Michael.

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > > [...] why don't you any end-of-line metacharacter, 
> > > i.e., `$' [1] in your above pattern?
> >
> > There's no reason to match end-of-line.
> > But you can match newline chars.
> 
> With other words: "$" _doesn't_ match a newline character, it just
> matches the position (the empty string) at a line's end.  If you want to
> have matches spanning lines, you must match newline characters in some
> way.

Yes, that's what I should have said.

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 5:10 AM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > `C-s (require . cl)'
> >
> > I tried again and it worked, as shown in the attachment.
> >
>
> > > Yes. `C-M-s' for this in *Help* for `C-h v load-history'.
> > >
> > > (require[
> > >  ]+[.][
> > >  ]+cl)
> >
> > Thank you for showing me this pattern. TBF, it seems to me that the
> > syntax of line spanning match pattern is very strange. It would be
> > nice if there were some explanation for how to build this pattern.
>
> See the Emacs manual, node `Lax Search'.  Depending on your
> value of option `search-whitespace-regexp' you can just
> type a space char to match one or more whitespace chars,
> including newline chars.  I you set it to "[
>
> ]+" (which corresponds to "[ \t\r\n]+" then you can just
> search with `C-s' for `(require . cl)'.  That will cross
> newlines.
>
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Lax-Search.html

Thank you very much for the information, but I still can't figure out
what's the meaning of `Lax' used here.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 5:16 AM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > Thank you for showing me this pattern. TBF, it seems to me that the
> > > syntax of line spanning match pattern is very strange. It would be
> > > nice if there were some explanation for how to build this pattern.
> >
> > To be more specifically, since this is a multiline match pattern, why
> > don't you any end-of-line metacharacter, i.e., `$' [1] in your above
> > pattern?
>
> There's no reason to match end-of-line.
> But you can match newline chars.

Got it. If we say end-of-line, it only means the end mark of a line,
so no line spanning in this meaning.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 6:39 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Drew Adams <drew.adams@oracle.com> writes:
>
> > > [...] why don't you any end-of-line metacharacter, i.e., `$' [1] in
> > > your above pattern?
> >
> > There's no reason to match end-of-line.
> > But you can match newline chars.
>
> With other words: "$" _doesn't_ match a newline character, it just
> matches the position (the empty string) at a line's end.  If you want to
> have matches spanning lines, you must match newline characters in some
> way.

Got it. Thank you very much.

> Michael.

Hongyi

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 5:14 AM Drew Adams <drew.adams@oracle.com> wrote:
>
> > Based on the guidance here [1], I tried the following two commands:
> >
> >  C-M-s                   incremental forward search matching regexp
> >  C-M-r                   incremental backward search matching regexp
> >
> > And it seems that, by default, the `C-M-r' is bound to
> > isearch-backward-regexp, while `C-M-s' is not bound to
> > isearch-forward-regexp.
>
> Start Emacs with `emacs -Q' (no init file), and I think
> `C-h k C-M-s' will tell you:
>
>   C-M-s runs the command isearch-forward-regexp

No, noting returned. I'm using self-compiled git master version of
Emacs on Ubuntu 20.04.

But `C-h k C-M-r' will tell me:

C-M-r runs the command isearch-backward-regexp

Best regards,
Hongyi

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> Thank you very much for the information, but I still can't figure out
> what's the meaning of `Lax' used here.

A strict interpretation of a space char you type
means match it against a single space char.

The lax interpretation of a space char you type
means match it against one or more chars, each
of which can be space, tab, newline, or carriage
return.

Look at the regexp that's in the string that's
the value of the variable when you opt for lax
matching of a space char.  That regexp says
just that: one or more of those chars.

Read the Elisp manual, node `Regular Expressions'
and its subnodes.

https://www.gnu.org/software/emacs/manual/html_node/elisp/Regular-Expressions.html

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > Start Emacs with `emacs -Q' (no init file), and I think
> > `C-h k C-M-s' will tell you:
> >
> >   C-M-s runs the command isearch-forward-regexp
> 
> No, noting returned. I'm using self-compiled git master version of
> Emacs on Ubuntu 20.04.

`M-x report-emacs-bug'

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 10:28 AM Drew Adams <drew.adams@oracle.com> wrote:
>
> > Thank you very much for the information, but I still can't figure out
> > what's the meaning of `Lax' used here.
>
> A strict interpretation of a space char you type
> means match it against a single space char.
>
> The lax interpretation of a space char you type
> means match it against one or more chars, each
> of which can be space, tab, newline, or carriage
> return.
>
> Look at the regexp that's in the string that's
> the value of the variable when you opt for lax
> matching of a space char.  That regexp says
> just that: one or more of those chars.
>
> Read the Elisp manual, node `Regular Expressions'
> and its subnodes.
>
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Regular-Expressions.html

Thank you again. I summarize the other manual nodes relevant to the
question discussed here as follows:

https://www.gnu.org/software/emacs/manual/html_node/elisp/Rx-Notation.html
https://www.gnu.org/software/emacs/manual/html_node/emacs/Lax-Search.html
https://www.gnu.org/software/emacs/manual/html_node/emacs/Replacement-and-Lax-Matches.html

Hongyi

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

> Thank you again. I summarize the other manual nodes relevant
> to the question discussed here as follows:
>
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Rx-Notation.html
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Lax-Search.html
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Replacement-and-Lax-Matches.html

(info "(elisp) Rx Notation")
(info "(emacs) Lax Search")
(info "(emacs) Replacement and Lax Matches")

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 10:30 AM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > Start Emacs with `emacs -Q' (no init file), and I think
> > > `C-h k C-M-s' will tell you:
> > >
> > >   C-M-s runs the command isearch-forward-regexp
> >
> > No, noting returned. I'm using self-compiled git master version of
> > Emacs on Ubuntu 20.04.
>
> `M-x report-emacs-bug'

I've done with the above command to prepare and send this bug report.
But, BTW, I haven't done any configuration for gnus [1], but instead,
I noticed the following `custom-set-variables' setting in my
`~/.emacs.d/init.el':

'(send-mail-function 'mailclient-send-it)

If I want to use gnus to do the job through my Gmail account, what
adjustments should I make?

[1] https://www.gnu.org/software/emacs/manual/html_node/gnus/

Best regards,
Hongyi

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> > Start Emacs with `emacs -Q' (no init file), and I think
> > `C-h k C-M-s' will tell you:
> >
> >   C-M-s runs the command isearch-forward-regexp
>
> No, noting returned. I'm using self-compiled git master version of
> Emacs on Ubuntu 20.04.

I'm using the same on Debian and it works.

What response do you get?  Or maybe you just hit a wrong key?  Or has
Drew maybe posted the wrong keys?...no, that looks ok.

The key could be occupied by the terminal or the window manager if Emacs
doesn't respond at all.

Michael.

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

On Sun, Aug 1, 2021 at 12:23 PM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > > Start Emacs with `emacs -Q' (no init file), and I think
> > > `C-h k C-M-s' will tell you:
> > >
> > >   C-M-s runs the command isearch-forward-regexp
> >
> > No, noting returned. I'm using self-compiled git master version of
> > Emacs on Ubuntu 20.04.
>
> I'm using the same on Debian and it works.
>
> What response do you get?  Or maybe you just hit a wrong key?  Or has
> Drew maybe posted the wrong keys?...no, that looks ok.
>
> The key could be occupied by the terminal or the window manager if Emacs
> doesn't respond at all.

Yeah, you're right. That key binding has already been occupied by
gpaste, as shown in the attachment. If I remove it from gpaste,
everything works the way it should in Emacs.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

[-- Attachment #2: Selection_007.png --]
[-- Type: image/png, Size: 82506 bytes --]

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 12:58 PM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
>
> On Sun, Aug 1, 2021 at 12:23 PM Michael Heerdegen
> <michael_heerdegen@web.de> wrote:
> >
> > Hongyi Zhao <hongyi.zhao@gmail.com> writes:
> >
> > > > Start Emacs with `emacs -Q' (no init file), and I think
> > > > `C-h k C-M-s' will tell you:
> > > >
> > > >   C-M-s runs the command isearch-forward-regexp
> > >
> > > No, noting returned. I'm using self-compiled git master version of
> > > Emacs on Ubuntu 20.04.
> >
> > I'm using the same on Debian and it works.
> >
> > What response do you get?  Or maybe you just hit a wrong key?  Or has
> > Drew maybe posted the wrong keys?...no, that looks ok.
> >
> > The key could be occupied by the terminal or the window manager if Emacs
> > doesn't respond at all.
>
> Yeah, you're right. That key binding has already been occupied by
> gpaste, as shown in the attachment. If I remove it from gpaste,
> everything works the way it should in Emacs.

After a second try, it seems that the `C-M-s' is still occupied by
other tools/utilities. I want to know whether there is a method to
pinpoint the culprit.

Hongyi

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > `M-x report-emacs-bug'
> 
> I've done with the above command to prepare and send this bug report.
> But, BTW, I haven't done any configuration for gnus [1], but instead,
> I noticed the following `custom-set-variables' setting in my
> `~/.emacs.d/init.el':
> 
> '(send-mail-function 'mailclient-send-it)
> 
> If I want to use gnus to do the job through my Gmail account, what
> adjustments should I make?

Someone else will answer that.  I don't use Emacs
for mail.  I use another mail client.  You can use
pretty much anything to send the mail.

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

> After a second try, it seems that the `C-M-s' is still
> occupied by other tools/utilities. I want to know whether
> there is a method to pinpoint the culprit.

It can be your window manager but also X utilities such
as xbindkeys.

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 1:46 PM Emanuel Berg via Users list for the GNU
Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> > After a second try, it seems that the `C-M-s' is still
> > occupied by other tools/utilities. I want to know whether
> > there is a method to pinpoint the culprit.
>
> It can be your window manager but also X utilities such
> as xbindkeys.

Until I read your post above, this tool was not installed on my computer.

Best regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

>>> After a second try, it seems that the `C-M-s' is still
>>> occupied by other tools/utilities. I want to know whether
>>> there is a method to pinpoint the culprit.
>>
>> It can be your window manager but also X utilities such
>> as xbindkeys.
>
> Until I read your post above, this tool was not installed on
> my computer.

(OK, well, don't use it I'd say, use the window manager
instead for that purpose, if needed.)

Please post the output of 'ps -e --forest'.

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 2:30 PM Emanuel Berg via Users list for the GNU
Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> >>> After a second try, it seems that the `C-M-s' is still
> >>> occupied by other tools/utilities. I want to know whether
> >>> there is a method to pinpoint the culprit.
> >>
> >> It can be your window manager but also X utilities such
> >> as xbindkeys.
> >
> > Until I read your post above, this tool was not installed on
> > my computer.
>
> (OK, well, don't use it I'd say, use the window manager
> instead for that purpose, if needed.)
>
> Please post the output of 'ps -e --forest'.

werner@X10DAi:~$ ps -e --forest
    PID TTY          TIME CMD
      2 ?        00:00:00 kthreadd
      3 ?        00:00:00  \_ rcu_gp
      4 ?        00:00:00  \_ rcu_par_gp
      5 ?        00:00:04  \_ kworker/0:0-events
      6 ?        00:00:00  \_ kworker/0:0H-kblockd
      9 ?        00:00:00  \_ kworker/u176:0-netns
     10 ?        00:00:00  \_ mm_percpu_wq
     11 ?        00:00:00  \_ ksoftirqd/0
     12 ?        00:00:52  \_ rcu_sched
     13 ?        00:00:00  \_ migration/0
     14 ?        00:00:00  \_ idle_inject/0
     15 ?        00:00:00  \_ cpuhp/0
     16 ?        00:00:00  \_ cpuhp/1
     17 ?        00:00:00  \_ idle_inject/1
     18 ?        00:00:00  \_ migration/1
     19 ?        00:00:00  \_ ksoftirqd/1
     21 ?        00:00:00  \_ kworker/1:0H-kblockd
     22 ?        00:00:00  \_ cpuhp/2
     23 ?        00:00:00  \_ idle_inject/2
     24 ?        00:00:00  \_ migration/2
     25 ?        00:00:00  \_ ksoftirqd/2
     27 ?        00:00:00  \_ kworker/2:0H-kblockd
     28 ?        00:00:00  \_ cpuhp/3
     29 ?        00:00:00  \_ idle_inject/3
     30 ?        00:00:00  \_ migration/3
     31 ?        00:00:00  \_ ksoftirqd/3
     33 ?        00:00:00  \_ kworker/3:0H-kblockd
     34 ?        00:00:00  \_ cpuhp/4
     35 ?        00:00:00  \_ idle_inject/4
     36 ?        00:00:00  \_ migration/4
     37 ?        00:00:00  \_ ksoftirqd/4
     39 ?        00:00:00  \_ kworker/4:0H-kblockd
     40 ?        00:00:00  \_ cpuhp/5
     41 ?        00:00:00  \_ idle_inject/5
     42 ?        00:00:00  \_ migration/5
     43 ?        00:00:00  \_ ksoftirqd/5
     45 ?        00:00:00  \_ kworker/5:0H-kblockd
     46 ?        00:00:00  \_ cpuhp/6
     47 ?        00:00:00  \_ idle_inject/6
     48 ?        00:00:00  \_ migration/6
     49 ?        00:00:00  \_ ksoftirqd/6
     51 ?        00:00:00  \_ kworker/6:0H-kblockd
     52 ?        00:00:00  \_ cpuhp/7
     53 ?        00:00:00  \_ idle_inject/7
     54 ?        00:00:00  \_ migration/7
     55 ?        00:00:00  \_ ksoftirqd/7
     57 ?        00:00:00  \_ kworker/7:0H-kblockd
     58 ?        00:00:00  \_ cpuhp/8
     59 ?        00:00:00  \_ idle_inject/8
     60 ?        00:00:00  \_ migration/8
     61 ?        00:00:00  \_ ksoftirqd/8
     63 ?        00:00:00  \_ kworker/8:0H-kblockd
     64 ?        00:00:00  \_ cpuhp/9
     65 ?        00:00:00  \_ idle_inject/9
     66 ?        00:00:00  \_ migration/9
     67 ?        00:00:00  \_ ksoftirqd/9
     68 ?        00:00:01  \_ kworker/9:0-rcu_gp
     69 ?        00:00:00  \_ kworker/9:0H-kblockd
     70 ?        00:00:00  \_ cpuhp/10
     71 ?        00:00:00  \_ idle_inject/10
     72 ?        00:00:00  \_ migration/10
     73 ?        00:00:00  \_ ksoftirqd/10
     75 ?        00:00:00  \_ kworker/10:0H-kblockd
     76 ?        00:00:00  \_ cpuhp/11
     77 ?        00:00:00  \_ idle_inject/11
     78 ?        00:00:00  \_ migration/11
     79 ?        00:00:00  \_ ksoftirqd/11
     81 ?        00:00:00  \_ kworker/11:0H-kblockd
     82 ?        00:00:00  \_ cpuhp/12
     83 ?        00:00:00  \_ idle_inject/12
     84 ?        00:00:00  \_ migration/12
     85 ?        00:00:00  \_ ksoftirqd/12
     87 ?        00:00:00  \_ kworker/12:0H
     88 ?        00:00:00  \_ cpuhp/13
     89 ?        00:00:00  \_ idle_inject/13
     90 ?        00:00:00  \_ migration/13
     91 ?        00:00:00  \_ ksoftirqd/13
     93 ?        00:00:00  \_ kworker/13:0H-kblockd
     94 ?        00:00:00  \_ cpuhp/14
     95 ?        00:00:00  \_ idle_inject/14
     96 ?        00:00:00  \_ migration/14
     97 ?        00:00:00  \_ ksoftirqd/14
     99 ?        00:00:00  \_ kworker/14:0H-kblockd
    100 ?        00:00:00  \_ cpuhp/15
    101 ?        00:00:00  \_ idle_inject/15
    102 ?        00:00:00  \_ migration/15
    103 ?        00:00:00  \_ ksoftirqd/15
    105 ?        00:00:00  \_ kworker/15:0H-kblockd
    106 ?        00:00:00  \_ cpuhp/16
    107 ?        00:00:00  \_ idle_inject/16
    108 ?        00:00:00  \_ migration/16
    109 ?        00:00:00  \_ ksoftirqd/16
    111 ?        00:00:00  \_ kworker/16:0H-kblockd
    112 ?        00:00:00  \_ cpuhp/17
    113 ?        00:00:00  \_ idle_inject/17
    114 ?        00:00:00  \_ migration/17
    115 ?        00:00:00  \_ ksoftirqd/17
    117 ?        00:00:00  \_ kworker/17:0H-kblockd
    118 ?        00:00:00  \_ cpuhp/18
    119 ?        00:00:00  \_ idle_inject/18
    120 ?        00:00:00  \_ migration/18
    121 ?        00:00:00  \_ ksoftirqd/18
    123 ?        00:00:00  \_ kworker/18:0H
    124 ?        00:00:00  \_ cpuhp/19
    125 ?        00:00:00  \_ idle_inject/19
    126 ?        00:00:00  \_ migration/19
    127 ?        00:00:00  \_ ksoftirqd/19
    129 ?        00:00:00  \_ kworker/19:0H-kblockd
    130 ?        00:00:00  \_ cpuhp/20
    131 ?        00:00:00  \_ idle_inject/20
    132 ?        00:00:00  \_ migration/20
    133 ?        00:00:00  \_ ksoftirqd/20
    135 ?        00:00:00  \_ kworker/20:0H-kblockd
    136 ?        00:00:00  \_ cpuhp/21
    137 ?        00:00:00  \_ idle_inject/21
    138 ?        00:00:00  \_ migration/21
    139 ?        00:00:00  \_ ksoftirqd/21
    140 ?        00:00:02  \_ kworker/21:0-events
    141 ?        00:00:00  \_ kworker/21:0H-kblockd
    142 ?        00:00:00  \_ cpuhp/22
    143 ?        00:00:00  \_ idle_inject/22
    144 ?        00:00:00  \_ migration/22
    145 ?        00:00:00  \_ ksoftirqd/22
    146 ?        00:00:00  \_ kworker/22:0-mm_percpu_wq
    147 ?        00:00:00  \_ kworker/22:0H
    149 ?        00:00:00  \_ cpuhp/23
    150 ?        00:00:00  \_ idle_inject/23
    151 ?        00:00:00  \_ migration/23
    152 ?        00:00:00  \_ ksoftirqd/23
    154 ?        00:00:00  \_ kworker/23:0H-kblockd
    155 ?        00:00:00  \_ cpuhp/24
    156 ?        00:00:00  \_ idle_inject/24
    157 ?        00:00:00  \_ migration/24
    158 ?        00:00:00  \_ ksoftirqd/24
    159 ?        00:00:00  \_ kworker/24:0-events
    160 ?        00:00:00  \_ kworker/24:0H-kblockd
    161 ?        00:00:00  \_ cpuhp/25
    162 ?        00:00:00  \_ idle_inject/25
    163 ?        00:00:00  \_ migration/25
    164 ?        00:00:00  \_ ksoftirqd/25
    166 ?        00:00:00  \_ kworker/25:0H-kblockd
    167 ?        00:00:00  \_ cpuhp/26
    168 ?        00:00:00  \_ idle_inject/26
    169 ?        00:00:00  \_ migration/26
    170 ?        00:00:00  \_ ksoftirqd/26
    172 ?        00:00:00  \_ kworker/26:0H-kblockd
    173 ?        00:00:00  \_ cpuhp/27
    174 ?        00:00:00  \_ idle_inject/27
    175 ?        00:00:00  \_ migration/27
    176 ?        00:00:00  \_ ksoftirqd/27
    178 ?        00:00:00  \_ kworker/27:0H-kblockd
    179 ?        00:00:00  \_ cpuhp/28
    180 ?        00:00:00  \_ idle_inject/28
    181 ?        00:00:00  \_ migration/28
    182 ?        00:00:00  \_ ksoftirqd/28
    183 ?        00:00:00  \_ kworker/28:0-mm_percpu_wq
    184 ?        00:00:00  \_ kworker/28:0H-kblockd
    185 ?        00:00:00  \_ cpuhp/29
    186 ?        00:00:00  \_ idle_inject/29
    187 ?        00:00:00  \_ migration/29
    188 ?        00:00:00  \_ ksoftirqd/29
    189 ?        00:00:00  \_ kworker/29:0-mm_percpu_wq
    190 ?        00:00:00  \_ kworker/29:0H
    191 ?        00:00:00  \_ cpuhp/30
    192 ?        00:00:00  \_ idle_inject/30
    193 ?        00:00:00  \_ migration/30
    194 ?        00:00:00  \_ ksoftirqd/30
    196 ?        00:00:00  \_ kworker/30:0H-kblockd
    197 ?        00:00:00  \_ cpuhp/31
    198 ?        00:00:00  \_ idle_inject/31
    199 ?        00:00:00  \_ migration/31
    200 ?        00:00:00  \_ ksoftirqd/31
    201 ?        00:00:00  \_ kworker/31:0-mm_percpu_wq
    202 ?        00:00:00  \_ kworker/31:0H
    203 ?        00:00:00  \_ cpuhp/32
    204 ?        00:00:00  \_ idle_inject/32
    205 ?        00:00:00  \_ migration/32
    206 ?        00:00:00  \_ ksoftirqd/32
    207 ?        00:00:00  \_ kworker/32:0-mm_percpu_wq
    208 ?        00:00:00  \_ kworker/32:0H
    209 ?        00:00:00  \_ cpuhp/33
    210 ?        00:00:00  \_ idle_inject/33
    211 ?        00:00:00  \_ migration/33
    212 ?        00:00:00  \_ ksoftirqd/33
    213 ?        00:00:00  \_ kworker/33:0-mm_percpu_wq
    214 ?        00:00:00  \_ kworker/33:0H-kblockd
    215 ?        00:00:00  \_ cpuhp/34
    216 ?        00:00:00  \_ idle_inject/34
    217 ?        00:00:00  \_ migration/34
    218 ?        00:00:00  \_ ksoftirqd/34
    220 ?        00:00:00  \_ kworker/34:0H-kblockd
    221 ?        00:00:00  \_ cpuhp/35
    222 ?        00:00:00  \_ idle_inject/35
    223 ?        00:00:00  \_ migration/35
    224 ?        00:00:00  \_ ksoftirqd/35
    226 ?        00:00:00  \_ kworker/35:0H-kblockd
    227 ?        00:00:00  \_ cpuhp/36
    228 ?        00:00:00  \_ idle_inject/36
    229 ?        00:00:00  \_ migration/36
    230 ?        00:00:00  \_ ksoftirqd/36
    232 ?        00:00:00  \_ kworker/36:0H-kblockd
    233 ?        00:00:00  \_ cpuhp/37
    234 ?        00:00:00  \_ idle_inject/37
    235 ?        00:00:00  \_ migration/37
    236 ?        00:00:00  \_ ksoftirqd/37
    238 ?        00:00:00  \_ kworker/37:0H-kblockd
    239 ?        00:00:00  \_ cpuhp/38
    240 ?        00:00:00  \_ idle_inject/38
    241 ?        00:00:00  \_ migration/38
    242 ?        00:00:00  \_ ksoftirqd/38
    243 ?        00:00:00  \_ kworker/38:0-mm_percpu_wq
    244 ?        00:00:00  \_ kworker/38:0H-kblockd
    245 ?        00:00:00  \_ cpuhp/39
    246 ?        00:00:00  \_ idle_inject/39
    247 ?        00:00:00  \_ migration/39
    248 ?        00:00:00  \_ ksoftirqd/39
    249 ?        00:00:00  \_ kworker/39:0-mm_percpu_wq
    250 ?        00:00:00  \_ kworker/39:0H
    251 ?        00:00:00  \_ cpuhp/40
    252 ?        00:00:00  \_ idle_inject/40
    253 ?        00:00:00  \_ migration/40
    254 ?        00:00:00  \_ ksoftirqd/40
    256 ?        00:00:00  \_ kworker/40:0H-kblockd
    257 ?        00:00:00  \_ cpuhp/41
    258 ?        00:00:00  \_ idle_inject/41
    259 ?        00:00:00  \_ migration/41
    260 ?        00:00:00  \_ ksoftirqd/41
    262 ?        00:00:00  \_ kworker/41:0H-kblockd
    263 ?        00:00:00  \_ cpuhp/42
    264 ?        00:00:00  \_ idle_inject/42
    265 ?        00:00:00  \_ migration/42
    266 ?        00:00:00  \_ ksoftirqd/42
    268 ?        00:00:00  \_ kworker/42:0H-kblockd
    269 ?        00:00:00  \_ cpuhp/43
    270 ?        00:00:00  \_ idle_inject/43
    271 ?        00:00:00  \_ migration/43
    272 ?        00:00:00  \_ ksoftirqd/43
    274 ?        00:00:00  \_ kworker/43:0H-kblockd
    275 ?        00:00:00  \_ cpuhp/44
    276 ?        00:00:00  \_ idle_inject/44
    277 ?        00:00:00  \_ migration/44
    278 ?        00:00:00  \_ ksoftirqd/44
    280 ?        00:00:00  \_ kworker/44:0H-kblockd
    281 ?        00:00:00  \_ cpuhp/45
    282 ?        00:00:00  \_ idle_inject/45
    283 ?        00:00:00  \_ migration/45
    284 ?        00:00:00  \_ ksoftirqd/45
    285 ?        00:00:00  \_ kworker/45:0-rcu_par_gp
    286 ?        00:00:00  \_ kworker/45:0H-kblockd
    287 ?        00:00:00  \_ cpuhp/46
    288 ?        00:00:00  \_ idle_inject/46
    289 ?        00:00:00  \_ migration/46
    290 ?        00:00:00  \_ ksoftirqd/46
    292 ?        00:00:00  \_ kworker/46:0H-kblockd
    293 ?        00:00:00  \_ cpuhp/47
    294 ?        00:00:00  \_ idle_inject/47
    295 ?        00:00:00  \_ migration/47
    296 ?        00:00:00  \_ ksoftirqd/47
    297 ?        00:00:00  \_ kworker/47:0-rcu_par_gp
    298 ?        00:00:00  \_ kworker/47:0H
    299 ?        00:00:00  \_ cpuhp/48
    300 ?        00:00:00  \_ idle_inject/48
    301 ?        00:00:00  \_ migration/48
    302 ?        00:00:00  \_ ksoftirqd/48
    304 ?        00:00:00  \_ kworker/48:0H
    305 ?        00:00:00  \_ cpuhp/49
    306 ?        00:00:00  \_ idle_inject/49
    307 ?        00:00:00  \_ migration/49
    308 ?        00:00:00  \_ ksoftirqd/49
    310 ?        00:00:00  \_ kworker/49:0H-kblockd
    311 ?        00:00:00  \_ cpuhp/50
    312 ?        00:00:00  \_ idle_inject/50
    313 ?        00:00:00  \_ migration/50
    314 ?        00:00:00  \_ ksoftirqd/50
    316 ?        00:00:00  \_ kworker/50:0H-kblockd
    317 ?        00:00:00  \_ cpuhp/51
    318 ?        00:00:00  \_ idle_inject/51
    319 ?        00:00:00  \_ migration/51
    320 ?        00:00:00  \_ ksoftirqd/51
    322 ?        00:00:00  \_ kworker/51:0H-kblockd
    323 ?        00:00:00  \_ cpuhp/52
    324 ?        00:00:00  \_ idle_inject/52
    325 ?        00:00:00  \_ migration/52
    326 ?        00:00:00  \_ ksoftirqd/52
    328 ?        00:00:00  \_ kworker/52:0H-kblockd
    329 ?        00:00:00  \_ cpuhp/53
    330 ?        00:00:00  \_ idle_inject/53
    331 ?        00:00:00  \_ migration/53
    332 ?        00:00:00  \_ ksoftirqd/53
    334 ?        00:00:00  \_ kworker/53:0H-kblockd
    335 ?        00:00:00  \_ cpuhp/54
    336 ?        00:00:00  \_ idle_inject/54
    337 ?        00:00:00  \_ migration/54
    338 ?        00:00:00  \_ ksoftirqd/54
    339 ?        00:00:01  \_ kworker/54:0-rcu_par_gp
    340 ?        00:00:00  \_ kworker/54:0H-kblockd
    341 ?        00:00:00  \_ cpuhp/55
    342 ?        00:00:00  \_ idle_inject/55
    343 ?        00:00:00  \_ migration/55
    344 ?        00:00:00  \_ ksoftirqd/55
    346 ?        00:00:00  \_ kworker/55:0H-kblockd
    347 ?        00:00:00  \_ cpuhp/56
    348 ?        00:00:00  \_ idle_inject/56
    349 ?        00:00:00  \_ migration/56
    350 ?        00:00:00  \_ ksoftirqd/56
    352 ?        00:00:00  \_ kworker/56:0H-kblockd
    353 ?        00:00:00  \_ cpuhp/57
    354 ?        00:00:00  \_ idle_inject/57
    355 ?        00:00:00  \_ migration/57
    356 ?        00:00:00  \_ ksoftirqd/57
    358 ?        00:00:00  \_ kworker/57:0H-kblockd
    359 ?        00:00:00  \_ cpuhp/58
    360 ?        00:00:00  \_ idle_inject/58
    361 ?        00:00:00  \_ migration/58
    362 ?        00:00:00  \_ ksoftirqd/58
    364 ?        00:00:00  \_ kworker/58:0H-kblockd
    365 ?        00:00:00  \_ cpuhp/59
    366 ?        00:00:00  \_ idle_inject/59
    367 ?        00:00:00  \_ migration/59
    368 ?        00:00:00  \_ ksoftirqd/59
    370 ?        00:00:00  \_ kworker/59:0H
    371 ?        00:00:00  \_ cpuhp/60
    372 ?        00:00:00  \_ idle_inject/60
    373 ?        00:00:00  \_ migration/60
    374 ?        00:00:00  \_ ksoftirqd/60
    375 ?        00:00:00  \_ kworker/60:0-rcu_par_gp
    376 ?        00:00:00  \_ kworker/60:0H-kblockd
    377 ?        00:00:00  \_ cpuhp/61
    378 ?        00:00:00  \_ idle_inject/61
    379 ?        00:00:00  \_ migration/61
    380 ?        00:00:00  \_ ksoftirqd/61
    381 ?        00:00:00  \_ kworker/61:0-rcu_par_gp
    382 ?        00:00:00  \_ kworker/61:0H-kblockd
    383 ?        00:00:00  \_ cpuhp/62
    384 ?        00:00:00  \_ idle_inject/62
    385 ?        00:00:00  \_ migration/62
    386 ?        00:00:00  \_ ksoftirqd/62
    387 ?        00:00:00  \_ kworker/62:0-mm_percpu_wq
    388 ?        00:00:00  \_ kworker/62:0H-kblockd
    389 ?        00:00:00  \_ cpuhp/63
    390 ?        00:00:00  \_ idle_inject/63
    391 ?        00:00:00  \_ migration/63
    392 ?        00:00:00  \_ ksoftirqd/63
    394 ?        00:00:00  \_ kworker/63:0H-kblockd
    395 ?        00:00:00  \_ cpuhp/64
    396 ?        00:00:00  \_ idle_inject/64
    397 ?        00:00:00  \_ migration/64
    398 ?        00:00:00  \_ ksoftirqd/64
    400 ?        00:00:00  \_ kworker/64:0H-kblockd
    401 ?        00:00:00  \_ cpuhp/65
    402 ?        00:00:00  \_ idle_inject/65
    403 ?        00:00:00  \_ migration/65
    404 ?        00:00:00  \_ ksoftirqd/65
    406 ?        00:00:00  \_ kworker/65:0H-kblockd
    407 ?        00:00:00  \_ cpuhp/66
    408 ?        00:00:00  \_ idle_inject/66
    409 ?        00:00:00  \_ migration/66
    410 ?        00:00:00  \_ ksoftirqd/66
    411 ?        00:00:00  \_ kworker/66:0-mm_percpu_wq
    412 ?        00:00:00  \_ kworker/66:0H-kblockd
    413 ?        00:00:00  \_ cpuhp/67
    414 ?        00:00:00  \_ idle_inject/67
    415 ?        00:00:00  \_ migration/67
    416 ?        00:00:00  \_ ksoftirqd/67
    418 ?        00:00:00  \_ kworker/67:0H-kblockd
    419 ?        00:00:00  \_ cpuhp/68
    420 ?        00:00:00  \_ idle_inject/68
    421 ?        00:00:00  \_ migration/68
    422 ?        00:00:00  \_ ksoftirqd/68
    424 ?        00:00:00  \_ kworker/68:0H-kblockd
    425 ?        00:00:00  \_ cpuhp/69
    426 ?        00:00:00  \_ idle_inject/69
    427 ?        00:00:00  \_ migration/69
    428 ?        00:00:00  \_ ksoftirqd/69
    430 ?        00:00:00  \_ kworker/69:0H-kblockd
    431 ?        00:00:00  \_ cpuhp/70
    432 ?        00:00:00  \_ idle_inject/70
    433 ?        00:00:00  \_ migration/70
    434 ?        00:00:00  \_ ksoftirqd/70
    436 ?        00:00:00  \_ kworker/70:0H-kblockd
    437 ?        00:00:00  \_ cpuhp/71
    438 ?        00:00:00  \_ idle_inject/71
    439 ?        00:00:00  \_ migration/71
    440 ?        00:00:00  \_ ksoftirqd/71
    442 ?        00:00:00  \_ kworker/71:0H
    443 ?        00:00:00  \_ cpuhp/72
    444 ?        00:00:00  \_ idle_inject/72
    445 ?        00:00:00  \_ migration/72
    446 ?        00:00:00  \_ ksoftirqd/72
    448 ?        00:00:00  \_ kworker/72:0H-kblockd
    449 ?        00:00:00  \_ cpuhp/73
    450 ?        00:00:00  \_ idle_inject/73
    451 ?        00:00:00  \_ migration/73
    452 ?        00:00:00  \_ ksoftirqd/73
    454 ?        00:00:00  \_ kworker/73:0H
    455 ?        00:00:00  \_ cpuhp/74
    456 ?        00:00:00  \_ idle_inject/74
    457 ?        00:00:00  \_ migration/74
    458 ?        00:00:00  \_ ksoftirqd/74
    460 ?        00:00:00  \_ kworker/74:0H-kblockd
    461 ?        00:00:00  \_ cpuhp/75
    462 ?        00:00:00  \_ idle_inject/75
    463 ?        00:00:00  \_ migration/75
    464 ?        00:00:00  \_ ksoftirqd/75
    465 ?        00:00:00  \_ kworker/75:0-rcu_par_gp
    466 ?        00:00:00  \_ kworker/75:0H-kblockd
    467 ?        00:00:00  \_ cpuhp/76
    468 ?        00:00:00  \_ idle_inject/76
    469 ?        00:00:00  \_ migration/76
    470 ?        00:00:00  \_ ksoftirqd/76
    472 ?        00:00:00  \_ kworker/76:0H-kblockd
    473 ?        00:00:00  \_ cpuhp/77
    474 ?        00:00:00  \_ idle_inject/77
    475 ?        00:00:00  \_ migration/77
    476 ?        00:00:00  \_ ksoftirqd/77
    478 ?        00:00:00  \_ kworker/77:0H-events_highpri
    479 ?        00:00:00  \_ cpuhp/78
    480 ?        00:00:00  \_ idle_inject/78
    481 ?        00:00:00  \_ migration/78
    482 ?        00:00:00  \_ ksoftirqd/78
    483 ?        00:00:00  \_ kworker/78:0-mm_percpu_wq
    484 ?        00:00:00  \_ kworker/78:0H
    485 ?        00:00:00  \_ cpuhp/79
    486 ?        00:00:00  \_ idle_inject/79
    487 ?        00:00:00  \_ migration/79
    488 ?        00:00:00  \_ ksoftirqd/79
    490 ?        00:00:00  \_ kworker/79:0H
    491 ?        00:00:00  \_ cpuhp/80
    492 ?        00:00:00  \_ idle_inject/80
    493 ?        00:00:00  \_ migration/80
    494 ?        00:00:00  \_ ksoftirqd/80
    496 ?        00:00:00  \_ kworker/80:0H-kblockd
    497 ?        00:00:00  \_ cpuhp/81
    498 ?        00:00:00  \_ idle_inject/81
    499 ?        00:00:00  \_ migration/81
    500 ?        00:00:00  \_ ksoftirqd/81
    502 ?        00:00:00  \_ kworker/81:0H-kblockd
    503 ?        00:00:00  \_ cpuhp/82
    504 ?        00:00:00  \_ idle_inject/82
    505 ?        00:00:00  \_ migration/82
    506 ?        00:00:00  \_ ksoftirqd/82
    508 ?        00:00:00  \_ kworker/82:0H-kblockd
    509 ?        00:00:00  \_ cpuhp/83
    510 ?        00:00:00  \_ idle_inject/83
    511 ?        00:00:00  \_ migration/83
    512 ?        00:00:00  \_ ksoftirqd/83
    513 ?        00:00:00  \_ kworker/83:0-mm_percpu_wq
    514 ?        00:00:00  \_ kworker/83:0H
    515 ?        00:00:00  \_ cpuhp/84
    516 ?        00:00:00  \_ idle_inject/84
    517 ?        00:00:00  \_ migration/84
    518 ?        00:00:00  \_ ksoftirqd/84
    520 ?        00:00:00  \_ kworker/84:0H
    521 ?        00:00:00  \_ cpuhp/85
    522 ?        00:00:00  \_ idle_inject/85
    523 ?        00:00:00  \_ migration/85
    524 ?        00:00:00  \_ ksoftirqd/85
    525 ?        00:00:00  \_ kworker/85:0-mm_percpu_wq
    526 ?        00:00:00  \_ kworker/85:0H-kblockd
    527 ?        00:00:00  \_ cpuhp/86
    528 ?        00:00:00  \_ idle_inject/86
    529 ?        00:00:00  \_ migration/86
    530 ?        00:00:00  \_ ksoftirqd/86
    531 ?        00:00:00  \_ kworker/86:0-mm_percpu_wq
    532 ?        00:00:00  \_ kworker/86:0H-kblockd
    533 ?        00:00:00  \_ cpuhp/87
    534 ?        00:00:00  \_ idle_inject/87
    535 ?        00:00:00  \_ migration/87
    536 ?        00:00:00  \_ ksoftirqd/87
    538 ?        00:00:00  \_ kworker/87:0H
    539 ?        00:00:00  \_ kdevtmpfs
    540 ?        00:00:00  \_ netns
    541 ?        00:00:00  \_ rcu_tasks_kthre
    542 ?        00:00:00  \_ kauditd
    544 ?        00:00:00  \_ kworker/1:2-rcu_par_gp
    545 ?        00:00:00  \_ kworker/2:1-rcu_gp
    547 ?        00:00:00  \_ khungtaskd
    548 ?        00:00:00  \_ oom_reaper
    549 ?        00:00:00  \_ writeback
    550 ?        00:00:00  \_ kcompactd0
    551 ?        00:00:00  \_ kcompactd1
    552 ?        00:00:00  \_ ksmd
    553 ?        00:00:00  \_ khugepaged
    647 ?        00:00:00  \_ kintegrityd
    648 ?        00:00:00  \_ kblockd
    649 ?        00:00:00  \_ blkcg_punt_bio
    651 ?        00:00:02  \_ kworker/47:1-mm_percpu_wq
    655 ?        00:00:02  \_ kworker/6:1-events
    656 ?        00:00:00  \_ kworker/8:1-events
    658 ?        00:00:02  \_ kworker/10:1-events
    659 ?        00:00:00  \_ kworker/11:1-rcu_gp
    660 ?        00:00:02  \_ kworker/12:1-mm_percpu_wq
    661 ?        00:00:02  \_ kworker/13:1-mm_percpu_wq
    663 ?        00:00:02  \_ kworker/15:1-mm_percpu_wq
    668 ?        00:00:01  \_ kworker/24:1-mm_percpu_wq
    670 ?        00:00:00  \_ kworker/19:1-rcu_par_gp
    671 ?        00:00:01  \_ kworker/25:1-rcu_par_gp
    672 ?        00:00:00  \_ kworker/20:1-rcu_gp
    674 ?        00:00:00  \_ kworker/26:1-rcu_par_gp
    676 ?        00:00:01  \_ kworker/28:1-mm_percpu_wq
    677 ?        00:00:01  \_ kworker/29:1-mm_percpu_wq
    678 ?        00:00:01  \_ kworker/30:1-mm_percpu_wq
    679 ?        00:00:01  \_ kworker/31:1-mm_percpu_wq
    681 ?        00:00:02  \_ kworker/44:1-events
    682 ?        00:00:01  \_ kworker/32:1-mm_percpu_wq
    683 ?        00:00:03  \_ kworker/45:1-events
    684 ?        00:00:01  \_ kworker/33:1-mm_percpu_wq
    687 ?        00:00:00  \_ kworker/34:1-rcu_gp
    688 ?        00:00:01  \_ kworker/35:1-mm_percpu_wq
    689 ?        00:00:00  \_ kworker/50:1-rcu_par_gp
    691 ?        00:00:00  \_ kworker/36:1-rcu_gp
    693 ?        00:00:01  \_ kworker/37:1-rcu_gp
    696 ?        00:00:01  \_ kworker/38:1-events
    697 ?        00:00:01  \_ kworker/55:1-rcu_par_gp
    699 ?        00:00:00  \_ kworker/39:1-events
    700 ?        00:00:02  \_ kworker/57:1-mm_percpu_wq
    701 ?        00:00:00  \_ kworker/40:1-rcu_par_gp
    702 ?        00:00:02  \_ kworker/58:1-mm_percpu_wq
    703 ?        00:00:02  \_ kworker/59:1-rcu_gp
    708 ?        00:00:03  \_ kworker/62:1-events
    710 ?        00:00:00  \_ kworker/43:1-events
    713 ?        00:00:00  \_ kworker/66:1-mm_percpu_wq
    715 ?        00:00:00  \_ kworker/68:1-rcu_gp
    716 ?        00:00:01  \_ kworker/69:1-mm_percpu_wq
    723 ?        00:00:00  \_ kworker/76:1-rcu_gp
    726 ?        00:00:00  \_ kworker/79:1-rcu_par_gp
    727 ?        00:00:01  \_ kworker/80:1-mm_percpu_wq
    729 ?        00:00:01  \_ kworker/82:1-mm_percpu_wq
    730 ?        00:00:00  \_ kworker/83:1-rcu_par_gp
    731 ?        00:00:00  \_ kworker/84:1-mm_percpu_wq
    732 ?        00:00:00  \_ kworker/85:1-events
    733 ?        00:00:00  \_ kworker/86:1-events
    734 ?        00:00:00  \_ kworker/87:1-mm_percpu_wq
    735 ?        00:00:00  \_ tpm_dev_wq
    736 ?        00:00:00  \_ ata_sff
    737 ?        00:00:00  \_ md
    738 ?        00:00:00  \_ edac-poller
    739 ?        00:00:00  \_ devfreq_wq
    740 ?        00:00:00  \_ watchdogd
    744 ?        00:00:00  \_ kswapd0
    745 ?        00:00:00  \_ kswapd1
    746 ?        00:00:00  \_ ecryptfs-kthrea
    749 ?        00:00:00  \_ kthrotld
    752 ?        00:00:00  \_ acpi_thermal_pm
    753 ?        00:00:00  \_ vfio-irqfd-clea
    754 ?        00:00:00  \_ kworker/0:2-events
    756 ?        00:00:00  \_ kworker/u176:1-efi_rts_wq
    757 ?        00:00:00  \_ ipv6_addrconf
    769 ?        00:00:00  \_ kstrp
    773 ?        00:00:00  \_ kworker/u179:0
    774 ?        00:00:00  \_ kworker/u180:0-xprtiod
    775 ?        00:00:00  \_ kworker/u181:0
    791 ?        00:00:00  \_ charger_manager
    871 ?        00:00:00  \_ kworker/44:2-rcu_par_gp
    886 ?        00:00:00  \_ scsi_eh_0
    887 ?        00:00:00  \_ scsi_tmf_0
    888 ?        00:00:00  \_ scsi_eh_1
    889 ?        00:00:00  \_ scsi_tmf_1
    890 ?        00:00:00  \_ scsi_eh_2
    891 ?        00:00:00  \_ scsi_tmf_2
    892 ?        00:00:00  \_ scsi_eh_3
    893 ?        00:00:00  \_ scsi_tmf_3
    896 ?        00:00:00  \_ scsi_eh_4
    897 ?        00:00:00  \_ scsi_tmf_4
    898 ?        00:00:00  \_ scsi_eh_5
    899 ?        00:00:00  \_ scsi_tmf_5
    900 ?        00:00:00  \_ scsi_eh_6
    901 ?        00:00:00  \_ scsi_tmf_6
    902 ?        00:00:00  \_ scsi_eh_7
    903 ?        00:00:00  \_ scsi_tmf_7
    904 ?        00:00:00  \_ scsi_eh_8
    905 ?        00:00:00  \_ scsi_tmf_8
    906 ?        00:00:00  \_ scsi_eh_9
    907 ?        00:00:00  \_ scsi_tmf_9
    928 ?        00:00:00  \_ raid5wq
    939 ?        00:00:00  \_ kworker/9:1H-events_highpri
    944 ?        00:00:00  \_ kworker/4:1H-kblockd
    947 ?        00:00:00  \_ kworker/14:1H-events_highpri
    949 ?        00:00:00  \_ kworker/10:2-events
    966 ?        00:00:00  \_ kworker/53:1H-events_highpri
    968 ?        00:00:00  \_ kworker/6:1H-kblockd
    969 ?        00:00:01  \_ jbd2/sdb1-8
    970 ?        00:00:00  \_ ext4-rsv-conver
    971 ?        00:00:00  \_ kworker/5:1H-events_highpri
    984 ?        00:00:00  \_ kworker/52:1H-events_highpri
    988 ?        00:00:00  \_ kworker/49:1H-events_highpri
    990 ?        00:00:00  \_ kworker/50:1H-events_highpri
    992 ?        00:00:00  \_ kworker/7:1H-events_highpri
   1015 ?        00:00:00  \_ kworker/11:1H-kblockd
   1016 ?        00:00:00  \_ kworker/45:1H-events_highpri
   1017 ?        00:00:00  \_ kworker/19:1H-events_highpri
   1020 ?        00:00:00  \_ kworker/59:1H-events_highpri
   1021 ?        00:00:00  \_ kworker/12:1H-events_highpri
   1025 ?        00:00:00  \_ kworker/56:1H-events_highpri
   1026 ?        00:00:00  \_ kworker/57:1H-events_highpri
   1030 ?        00:00:00  \_ kworker/16:1H-events_highpri
   1033 ?        00:00:00  \_ kworker/17:1H-events_highpri
   1034 ?        00:00:00  \_ kworker/18:1H-events_highpri
   1035 ?        00:00:00  \_ kworker/61:1H-events_highpri
   1036 ?        00:00:00  \_ kworker/15:1H-events_highpri
   1037 ?        00:00:00  \_ kworker/60:1H-events_highpri
   1057 ?        00:00:00  \_ kworker/64:1H-events_highpri
   1061 ?        00:00:00  \_ kworker/1:1H-kblockd
   1063 ?        00:00:00  \_ kworker/0:1H-kblockd
   1070 ?        00:00:00  \_ rpciod
   1071 ?        00:00:00  \_ xprtiod
   1074 ?        00:00:00  \_ kworker/10:1H-events_highpri
   1078 ?        00:00:00  \_ kworker/2:1H-events_highpri
   1081 ?        00:00:00  \_ kworker/3:1H-events_highpri
   1084 ?        00:00:00  \_ kworker/51:1H-events_highpri
   1094 ?        00:00:00  \_ kworker/62:1H-events_highpri
   1096 ?        00:00:00  \_ loop0
   1106 ?        00:00:00  \_ loop1
   1116 ?        00:00:00  \_ loop2
   1117 ?        00:00:00  \_ loop3
   1118 ?        00:00:00  \_ kworker/8:1H-events_highpri
   1119 ?        00:00:00  \_ loop4
   1120 ?        00:00:00  \_ loop5
   1121 ?        00:00:00  \_ kworker/65:1H-events_highpri
   1156 ?        00:00:00  \_ loop6
   1157 ?        00:00:00  \_ kworker/13:1H-events_highpri
   1209 ?        00:00:00  \_ loop7
   1210 ?        00:00:00  \_ kworker/42:1H-events_highpri
   1211 ?        00:00:00  \_ kworker/43:1H-kblockd
   1212 ?        00:00:00  \_ kworker/76:1H-events_highpri
   1213 ?        00:00:00  \_ kworker/77:1H
   1214 ?        00:00:00  \_ kworker/36:1H-kblockd
   1289 ?        00:00:00  \_ loop8
   1290 ?        00:00:00  \_ kworker/63:1H-events_highpri
   1327 ?        00:00:00  \_ loop9
   1328 ?        00:00:00  \_ kworker/69:1H-events_highpri
   1329 ?        00:00:00  \_ kworker/23:1H-kblockd
   1330 ?        00:00:00  \_ kworker/74:1H-events_highpri
   1331 ?        00:00:00  \_ loop10
   1333 ?        00:00:00  \_ kworker/44:1H-events_highpri
   1334 ?        00:00:00  \_ kworker/54:1H-events_highpri
   1335 ?        00:00:00  \_ kworker/71:1H-events_highpri
   1336 ?        00:00:00  \_ kworker/47:1H-events_highpri
   1337 ?        00:00:00  \_ kworker/82:1H-events_highpri
   1338 ?        00:00:00  \_ kworker/86:1H-events_highpri
   1339 ?        00:00:00  \_ kworker/20:1H-events_highpri
   1340 ?        00:00:00  \_ kworker/83:1H-events_highpri
   1341 ?        00:00:00  \_ kworker/34:1H-events_highpri
   1342 ?        00:00:00  \_ kworker/38:1H-events_highpri
   1343 ?        00:00:00  \_ kworker/32:1H-events_highpri
   1344 ?        00:00:00  \_ kworker/27:1H-events_highpri
   1345 ?        00:00:00  \_ kworker/33:1H-events_highpri
   1346 ?        00:00:00  \_ kworker/40:1H-kblockd
   1347 ?        00:00:00  \_ kworker/75:1H-kblockd
   1348 ?        00:00:00  \_ kworker/87:1H-events_highpri
   1349 ?        00:00:00  \_ kworker/80:1H-events_highpri
   1350 ?        00:00:00  \_ kworker/67:1H-events_highpri
   1351 ?        00:00:00  \_ kworker/25:1H-kblockd
   1352 ?        00:00:00  \_ kworker/35:1H-kblockd
   1353 ?        00:00:00  \_ kworker/73:1H-events_highpri
   1354 ?        00:00:00  \_ kworker/85:1H-events_highpri
   1355 ?        00:00:00  \_ kworker/30:1H-events_highpri
   1361 ?        00:00:00  \_ loop11
   1362 ?        00:00:00  \_ kworker/84:2-events
   1365 ?        00:00:00  \_ kworker/24:1H-kblockd
   1373 ?        00:00:00  \_ kworker/68:1H-events_highpri
   1387 ?        00:00:00  \_ loop12
   1388 ?        00:00:00  \_ kworker/26:1H-events_highpri
   1389 ?        00:00:00  \_ kworker/57:2-rcu_par_gp
   1399 ?        00:00:00  \_ kworker/28:1H-kblockd
   1400 ?        00:00:00  \_ loop13
   1401 ?        00:00:00  \_ kworker/72:1H-events_highpri
   1404 ?        00:00:00  \_ kworker/37:1H-kblockd
   1411 ?        00:00:00  \_ kworker/81:1H-events_highpri
   1412 ?        00:00:00  \_ kworker/41:1H-events_highpri
   1413 ?        00:00:00  \_ loop14
   1420 ?        00:00:00  \_ loop15
   1421 ?        00:00:00  \_ loop16
   1436 ?        00:00:00  \_ kworker/30:2
   1437 ?        00:00:00  \_ kworker/66:1H-events_highpri
   1438 ?        00:00:00  \_ loop17
   1441 ?        00:00:00  \_ irq/36-0-0008
   1444 ?        00:00:00  \_ cryptd
   1445 ?        00:00:02  \_ kworker/46:2-mm_percpu_wq
   1446 ?        00:00:00  \_ kworker/58:1H-events_highpri
   1462 ?        00:00:00  \_ nv_queue
   1463 ?        00:00:00  \_ nv_queue
   1479 ?        00:00:00  \_ kworker/39:1H-events_highpri
   1488 ?        00:00:00  \_ kworker/22:1H-kblockd
   1491 ?        00:00:00  \_ kworker/31:1H-events_highpri
   1492 ?        00:00:00  \_ nvidia-modeset/
   1493 ?        00:00:00  \_ nvidia-modeset/
   1529 ?        00:00:00  \_ UVM global queu
   1530 ?        00:00:00  \_ UVM deferred re
   1534 ?        00:00:00  \_ UVM Tools Event
   1555 ?        00:00:00  \_ kworker/29:1H-events_highpri
   1562 ?        00:00:00  \_ kworker/79:1H-kblockd
   1564 ?        00:00:00  \_ kworker/78:1H-kblockd
   1577 ?        00:00:00  \_ kworker/48:1H-events_highpri
   1614 ?        00:00:01  \_ kworker/26:2-events
   1615 ?        00:00:00  \_ kworker/42:2-mm_percpu_wq
   1617 ?        00:00:01  \_ kworker/27:2-mm_percpu_wq
   1649 ?        00:00:00  \_ kworker/70:1H-events_highpri
   1650 ?        00:00:00  \_ kworker/43:2-mm_percpu_wq
   1710 ?        00:00:00  \_ kworker/21:1H-events_highpri
   1737 ?        00:00:02  \_ kworker/11:2-mm_percpu_wq
   1738 ?        00:00:00  \_ kworker/13:2-events
   1746 ?        00:02:59  \_ irq/71-nvidia
   1747 ?        00:00:00  \_ nvidia
   1748 ?        00:00:03  \_ nv_queue
   1876 ?        00:00:00  \_ kworker/70:2-mm_percpu_wq
   1909 ?        00:00:00  \_ kworker/55:1H-events_highpri
   1932 ?        00:00:02  \_ kworker/56:2-mm_percpu_wq
   2067 ?        00:00:00  \_ kworker/84:1H-events_highpri
   2085 ?        00:00:00  \_ kworker/u180:1
   2087 ?        00:00:00  \_ lockd
   2103 ?        00:00:00  \_ kworker/15:2-rcu_par_gp
   2125 ?        00:00:00  \_ kworker/46:1H-events_highpri
   2206 ?        00:00:00  \_ nfsd
   2207 ?        00:00:00  \_ nfsd
   2208 ?        00:00:00  \_ nfsd
   2209 ?        00:00:00  \_ nfsd
   2210 ?        00:00:00  \_ nfsd
   2211 ?        00:00:00  \_ nfsd
   2212 ?        00:00:00  \_ nfsd
   2213 ?        00:00:00  \_ nfsd
   2231 ?        00:00:00  \_ kworker/7:2-events
   2250 ?        00:00:00  \_ kworker/46:3-rcu_par_gp
   2307 ?        00:00:00  \_ none
   2349 ?        00:00:00  \_ kworker/58:2
   2817 ?        00:00:02  \_ kworker/60:2-mm_percpu_wq
   2942 ?        00:00:00  \_ kworker/87:2
   2949 ?        00:00:00  \_ kworker/80:2-rcu_par_gp
   3494 ?        00:00:03  \_ kworker/20:2-events
   4054 ?        00:00:00  \_ kworker/69:2-rcu_par_gp
   4225 ?        00:00:01  \_ jbd2/sda1-8
   4226 ?        00:00:00  \_ ext4-rsv-conver
   4498 ?        00:00:02  \_ kworker/61:4-events
   5288 ?        00:00:00  \_ kworker/72:2-mm_percpu_wq
   7170 ?        00:00:01  \_ kworker/34:2-events
  49347 ?        00:00:01  \_ kworker/67:2-mm_percpu_wq
  49646 ?        00:00:02  \_ kworker/63:2-events
  66022 ?        00:00:03  \_ kworker/19:2-events
  66031 ?        00:00:00  \_ kworker/21:1-rcu_par_gp
  66608 ?        00:00:01  \_ kworker/48:2-rcu_par_gp
  66611 ?        00:00:02  \_ kworker/50:2-events
  88503 ?        00:00:00  \_ kworker/12:0
  88534 ?        00:00:00  \_ kworker/64:2-rcu_par_gp
  88563 ?        00:00:00  \_ kworker/41:2-cgroup_destroy
  88701 ?        00:00:00  \_ kworker/65:0-rcu_gp
 109824 ?        00:00:00  \_ kworker/27:0
 135407 ?        00:00:01  \_ kworker/71:3-rcu_par_gp
 468161 ?        00:00:02  \_ kworker/7:0-mm_percpu_wq
 599194 ?        00:00:01  \_ kworker/14:1-rcu_gp
 599203 ?        00:00:01  \_ kworker/16:1-events
 599221 ?        00:00:02  \_ kworker/18:1-rcu_gp
 621698 ?        00:00:02  \_ kworker/64:0-events
 865832 ?        00:00:02  \_ kworker/65:2-events
 866077 ?        00:00:02  \_ kworker/17:0-events
2336468 ?        00:00:00  \_ kworker/17:1-rcu_par_gp
3255703 ?        00:00:03  \_ kworker/2:2-mm_percpu_wq
3862112 ?        00:00:01  \_ kworker/8:0-mm_percpu_wq
3931182 ?        00:00:02  \_ kworker/1:1-events
4147209 ?        00:00:01  \_ kworker/3:0-events
 730559 ?        00:00:00  \_ kworker/63:0-events
3953433 ?        00:00:00  \_ kworker/35:0
3953434 ?        00:00:00  \_ kworker/36:2-mm_percpu_wq
3953437 ?        00:00:01  \_ kworker/37:0-events
4051932 ?        00:00:00  \_ kworker/53:0-rcu_par_gp
4051947 ?        00:00:00  \_ kworker/54:1-mm_percpu_wq
4051971 ?        00:00:00  \_ kworker/55:0-mm_percpu_wq
4075337 ?        00:00:01  \_ kworker/14:0-events
4075362 ?        00:00:00  \_ kworker/40:2-mm_percpu_wq
4075365 ?        00:00:00  \_ kworker/41:0-mm_percpu_wq
4075519 ?        00:00:00  \_ kworker/42:0
 267902 ?        00:00:00  \_ kworker/68:0-events
 267904 ?        00:00:00  \_ kworker/67:0
 331088 ?        00:00:01  \_ kworker/16:2-events
1337805 ?        00:00:00  \_ kworker/71:0-mm_percpu_wq
1337806 ?        00:00:00  \_ kworker/70:1-events
1517428 ?        00:00:00  \_ kworker/49:0-rcu_par_gp
1517435 ?        00:00:00  \_ kworker/51:1-rcu_par_gp
1517455 ?        00:00:00  \_ kworker/53:2-mm_percpu_wq
1540254 ?        00:00:00  \_ kworker/9:1-mm_percpu_wq
1540285 ?        00:00:00  \_ kworker/72:0-cgroup_destroy
1540286 ?        00:00:00  \_ kworker/73:2-rcu_par_gp
1540324 ?        00:00:01  \_ kworker/3:1-events
1683685 ?        00:00:00  \_ kworker/52:0-rcu_par_gp
1870591 ?        00:00:00  \_ kworker/73:0-mm_percpu_wq
1872918 ?        00:00:00  \_ kworker/75:3-events
1873083 ?        00:00:00  \_ kworker/74:5-mm_percpu_wq
1873091 ?        00:00:00  \_ kworker/74:7-events
1930464 ?        00:00:00  \_ kworker/76:2-mm_percpu_wq
1930465 ?        00:00:00  \_ kworker/77:0-rcu_par_gp
2272815 ?        00:00:00  \_ kworker/49:2-mm_percpu_wq
2272821 ?        00:00:00  \_ kworker/51:2-mm_percpu_wq
2275292 ?        00:00:00  \_ kworker/48:1-mm_percpu_wq
2275309 ?        00:00:00  \_ kworker/52:1-mm_percpu_wq
2295690 ?        00:00:00  \_ kworker/18:2-events
2298149 ?        00:00:00  \_ kworker/77:1-mm_percpu_wq
2298150 ?        00:00:00  \_ kworker/78:2-rcu_par_gp
2407906 ?        00:00:00  \_ kworker/79:2-mm_percpu_wq
2408039 ?        00:00:00  \_ kworker/81:0-rcu_par_gp
2877072 ?        00:00:00  \_ kworker/56:0
3116424 ?        00:00:00  \_ kworker/5:1-events
3202460 ?        00:00:00  \_ kworker/u178:1-events_unbound
3626911 ?        00:00:00  \_ kworker/4:1-events
3648119 ?        00:00:00  \_ kworker/59:0-mm_percpu_wq
3648164 ?        00:00:00  \_ kworker/81:1-mm_percpu_wq
3648167 ?        00:00:00  \_ kworker/82:2-rcu_par_gp
3648197 ?        00:00:00  \_ kworker/5:2
  78899 ?        00:00:00  \_ kworker/4:0-events
 137454 ?        00:00:00  \_ kworker/u177:0-events_power_efficient
 347430 ?        00:00:00  \_ kworker/23:2-rcu_par_gp
 347431 ?        00:00:00  \_ kworker/22:2
 405327 ?        00:00:00  \_ kworker/6:2-events
 541639 ?        00:00:00  \_ kworker/u177:1-events_power_efficient
 731030 ?        00:00:00  \_ kworker/u178:0-events_unbound
1057784 ?        00:00:00  \_ kworker/23:0-mm_percpu_wq
1057785 ?        00:00:00  \_ kworker/24:2-events
1245851 ?        00:00:00  \_ kworker/25:2-rcu_par_gp
1356077 ?        00:00:00  \_ kworker/24:3
1412663 ?        00:00:00  \_ kworker/u178:2-events_unbound
1442779 ?        00:00:00  \_ kworker/u177:2-events_power_efficient
1455657 ?        00:00:00  \_ kworker/10:0-mm_percpu_wq
1455696 ?        00:00:00  \_ kworker/10:3
1459961 ?        00:00:00  \_ kworker/u178:3-events_unbound
1520563 ?        00:00:00  \_ kworker/25:0-events
      1 ?        00:00:23 systemd
   1051 ?        00:00:12 systemd-journal
   1076 ?        00:00:00 blkmapd
   1115 ?        00:00:01 systemd-udevd
   1560 ?        00:00:00 rpc.idmapd
   1610 ?        00:00:00 rpcbind
   1612 ?        00:00:00 systemd-timesyn
   1641 ?        00:00:01 ovsdb-server
   1656 ?        00:00:01 accounts-daemon
   1658 ?        00:00:01 acpid
   1665 ?        00:00:00 avahi-daemon
   1743 ?        00:00:00  \_ avahi-daemon
   1666 ?        00:00:00 cron
   1668 ?        00:00:01 dbus-daemon
   1676 ?        00:00:07 irqbalance
   1680 ?        00:00:00 networkd-dispat
   1698 ?        00:00:00 polkitd
   1704 ?        00:00:03 rsyslogd
   1716 ?        00:00:06 snapd
   1724 ?        00:00:01 nvidia-persiste
   1725 ?        00:00:00 switcheroo-cont
   1726 ?        00:00:01 systemd-logind
   1727 ?        00:00:00 systemd-machine
   1729 ?        00:00:05 udisksd
   1734 ?        00:00:00 wpa_supplicant
   1740 ?        00:00:00 atd
   1829 ?        00:00:00 vmware-usbarbit
   1853 ?        00:00:00 ovs-vswitchd
   1880 ?        00:00:00 colord
   1886 ?        00:00:00 cups-browsed
   1917 ?        00:00:00 ModemManager
   1923 ?        00:00:00 cupsd
   1982 ?        00:00:00 uml_switch
   1985 ?        00:00:00 rpc.mountd
   2033 ?        00:00:07 containerd
   2034 ?        00:00:00 sshd
   2100 ?        00:00:00 gdm3
   2110 ?        00:00:00  \_ gdm-session-wor
   2249 tty1     00:00:00  |   \_ gdm-x-session
   2255 tty1     00:00:01  |       \_ Xorg
   2553 tty1     00:00:00  |       \_ gnome-session-b
   4075 ?        00:00:00  \_ gdm-session-wor
   4191 tty2     00:00:00      \_ gdm-x-session
   4193 tty2     00:20:09          \_ Xorg
   4204 tty2     00:00:00          \_ gnome-session-b
   4639 tty2     01:09:13              \_ Xsession
  53349 tty2     00:00:43              \_ fcitx5
   2108 ?        00:00:00 sndiod
   2109 ?        00:00:00 libvirtd
   2186 ?        00:00:00 systemd
   2193 ?        00:00:00  \_ (sd-pam)
   2246 ?        00:00:00  \_ pulseaudio
   2248 ?        00:00:00  \_ tracker-miner-f
   2305 ?        00:00:00  \_ dbus-daemon
   2392 ?        00:00:00  \_ gvfsd
   2420 ?        00:00:00  \_ gvfsd-fuse
   2436 ?        00:00:03  \_ gvfs-udisks2-vo
   2456 ?        00:00:00  \_ gvfs-mtp-volume
   2469 ?        00:00:00  \_ gvfs-afc-volume
   2478 ?        00:00:00  \_ gvfs-gphoto2-vo
   2484 ?        00:00:00  \_ gvfs-goa-volume
   2491 ?        00:00:00  \_ goa-daemon
   2506 ?        00:00:01  \_ goa-identity-se
   2570 ?        00:00:00  \_ at-spi-bus-laun
   2575 ?        00:00:00  |   \_ dbus-daemon
   2583 ?        00:00:00  \_ gnome-session-c
   2588 ?        00:00:00  \_ gnome-keyring-d
   2596 ?        00:00:00  \_ gnome-session-b
   2603 ?        00:00:12  \_ gnome-shell
   2649 ?        00:00:00  |   \_ ibus-daemon
   2652 ?        00:00:00  |       \_ ibus-memconf
   2727 ?        00:00:00  |       \_ ibus-engine-sim
   2655 ?        00:00:00  \_ ibus-x11
   2657 ?        00:00:00  \_ ibus-portal
   2667 ?        00:00:00  \_ at-spi2-registr
   2670 ?        00:00:00  \_ xdg-permission-
   2685 ?        00:00:00  \_ gjs
   2701 ?        00:00:00  \_ gsd-a11y-settin
   2702 ?        00:00:00  \_ gsd-color
   2703 ?        00:00:00  \_ gsd-keyboard
   2705 ?        00:00:00  \_ gsd-media-keys
   2707 ?        00:00:00  \_ gsd-power
   2709 ?        00:00:00  \_ gsd-print-notif
   2710 ?        00:00:00  \_ gsd-rfkill
   2713 ?        00:00:00  \_ gsd-smartcard
   2715 ?        00:00:00  \_ gsd-sound
   2717 ?        00:00:00  \_ gsd-usb-protect
   2718 ?        00:00:00  \_ gsd-wacom
   2719 ?        00:00:00  \_ gsd-wwan
   2721 ?        00:00:00  \_ gsd-xsettings
   2762 ?        00:00:00  \_ gsd-printer
   2274 ?        00:00:00 rtkit-daemon
   2464 ?        00:00:00 dnsmasq
   2465 ?        00:00:00  \_ dnsmasq
   2508 ?        00:00:00 upowerd
   2883 ?        00:00:00 microsocks
   2890 ?        00:00:00 whoopsie
   2898 ?        00:00:00 kerneloops
   2902 ?        00:00:00 kerneloops
   2968 ?        00:00:00 vmnet-bridge
   2998 ?        00:00:00 vmnet-netifup
   3018 ?        00:00:00 vmnet-dhcpd
   3025 ?        00:00:00 vmnet-natd
   3031 ?        00:00:00 vmnet-netifup
   3043 ?        00:00:00 vmnet-dhcpd
   4043 ?        00:00:00 master
   4045 ?        00:00:00  \_ qmgr
 141469 ?        00:00:00  \_ cleanup
 183235 ?        00:00:00  \_ trivial-rewrite
 204747 ?        00:00:00  \_ pickup
 265507 ?        00:00:00  \_ local
   4101 ?        00:00:01 systemd
   4106 ?        00:00:00  \_ (sd-pam)
   4114 ?        00:02:54  \_ pulseaudio
   4122 ?        00:00:22  \_ dbus-daemon
   4139 ?        00:00:00  \_ gvfsd
  66243 ?        00:00:00  |   \_ gvfsd-trash
 599200 ?        00:00:00  |   \_ gvfsd-network
 601846 ?        00:00:00  |   \_ gvfsd-dnssd
   4144 ?        00:00:00  \_ gvfsd-fuse
   4146 ?        00:00:03  \_ gvfs-udisks2-vo
   4159 ?        00:00:00  \_ gvfs-mtp-volume
   4163 ?        00:00:00  \_ gvfs-afc-volume
   4168 ?        00:00:00  \_ gvfs-gphoto2-vo
   4172 ?        00:00:00  \_ gvfs-goa-volume
   4176 ?        00:00:00  \_ goa-daemon
   4183 ?        00:00:01  \_ goa-identity-se
  62976 ?        00:00:00  \_ at-spi-bus-laun
  62991 ?        00:00:01  |   \_ dbus-daemon
  63115 ?        00:00:00  \_ gnome-session-c
  63140 ?        00:00:00  \_ gnome-session-b
  66456 ?        00:00:00  |   \_ gsd-disk-utilit
  66499 ?        00:00:00  |   \_ evolution-alarm
  66511 ?        00:01:12  |   \_ goldendict
  66518 ?        00:00:08  |   \_ kdeconnectd
  63220 ?        00:00:00  \_ gnome-keyring-d
  63245 ?        00:12:37  \_ gnome-shell
1890042 ?        00:15:34  |   \_ firefox-bin
1890901 ?        00:00:00  |       \_ Socket Process
1891419 ?        00:01:24  |       \_ WebExtensions
1891889 ?        00:00:07  |       \_ Privileged Cont
1892187 ?        00:04:31  |       \_ Web Content
1894955 ?        00:00:00  |       \_ RDD Process
2168741 ?        00:03:57  |       \_ Web Content
1034545 ?        00:00:00  |       \_ Web Content
  65786 ?        00:00:00  \_ xdg-permission-
  65897 ?        00:00:00  \_ gnome-shell-cal
  65977 ?        00:00:00  \_ evolution-sourc
  66238 ?        00:00:00  \_ gjs
  66245 ?        00:00:04  \_ at-spi2-registr
  66381 ?        00:00:00  \_ gsd-a11y-settin
  66384 ?        00:00:00  \_ gsd-color
  66385 ?        00:00:00  \_ gsd-datetime
  66389 ?        00:00:00  \_ gsd-housekeepin
  66394 ?        00:00:00  \_ gsd-keyboard
  66399 ?        00:00:00  \_ gsd-media-keys
  66401 ?        00:00:00  \_ gsd-power
  66404 ?        00:00:00  \_ gsd-print-notif
  66408 ?        00:00:00  \_ gsd-rfkill
  66412 ?        00:00:00  \_ gsd-screensaver
  66414 ?        00:00:00  \_ gsd-sharing
  66417 ?        00:00:00  \_ gsd-smartcard
  66419 ?        00:00:00  \_ gsd-sound
  66425 ?        00:00:00  \_ gsd-usb-protect
  66428 ?        00:00:00  \_ gsd-wacom
  66433 ?        00:00:00  \_ gsd-wwan
  66439 ?        00:00:00  \_ gsd-xsettings
  66451 ?        00:00:00  \_ evolution-calen
  66454 ?        00:03:09  \_ gpaste-daemon
  66498 ?        00:00:00  \_ gsd-printer
  66622 ?        00:00:00  \_ bash
  66715 ?        00:00:00  |   \_ proxychains4-da
  66716 ?        00:00:13  |   \_ chrome
  66814 ?        00:00:00  |       \_ cat
  66815 ?        00:00:00  |       \_ cat
  74309 ?        00:00:00  |       \_ chrome
  83613 ?        00:06:46  |       |   \_ chrome
  84331 ?        00:00:00  |       |       \_ chrome
  74366 ?        00:00:00  |       \_ chrome
  75976 ?        00:00:00  |       |   \_ nacl_helper
  76213 ?        00:00:00  |       |   \_ chrome
  84674 ?        00:00:00  |       |       \_ chrome
  91656 ?        00:00:00  |       |       \_ chrome
  91659 ?        00:00:00  |       |       \_ chrome
  91783 ?        00:00:05  |       |       \_ chrome
  83653 ?        00:00:00  |       \_ chrome
  66762 ?        00:00:00  \_ dconf-service
  66893 ?        00:00:00  \_ evolution-addre
  68486 ?        00:00:00  \_ gvfsd-metadata
 119809 ?        00:00:56  \_ gnome-terminal-
 120762 pts/0    00:00:00  |   \_ bash
 124510 pts/0    00:00:10  |   |   \_ bash
 124911 pts/0    00:00:01  |   |       \_ ss_local
 124925 pts/0    00:00:02  |   |       \_ ss_local
 124939 pts/0    00:00:01  |   |       \_ ss_local
 124952 pts/0    00:00:01  |   |       \_ ss_local
 124965 pts/0    00:00:01  |   |       \_ ss_local
 124979 pts/0    00:00:01  |   |       \_ ss_local
 124993 pts/0    00:00:01  |   |       \_ ss_local
 125007 pts/0    00:00:01  |   |       \_ ss_local
 125021 pts/0    00:00:01  |   |       \_ ss_local
 125034 pts/0    00:00:01  |   |       \_ ss_local
 125049 pts/0    00:00:02  |   |       \_ ss_local
 125061 pts/0    00:00:01  |   |       \_ ss_local
 125075 pts/0    00:00:01  |   |       \_ ss_local
 125089 pts/0    00:00:04  |   |       \_ ss_local
 125103 pts/0    00:00:01  |   |       \_ ss_local
 125115 pts/0    00:00:01  |   |       \_ ss_local
 125129 pts/0    00:00:01  |   |       \_ ss_local
 125143 pts/0    00:00:01  |   |       \_ ss_local
 125157 pts/0    00:00:01  |   |       \_ ss_local
 125171 pts/0    00:00:01  |   |       \_ ss_local
 125185 pts/0    00:00:01  |   |       \_ ss_local
 125199 pts/0    00:00:01  |   |       \_ ss_local
 125212 pts/0    00:00:01  |   |       \_ ss_local
 125225 pts/0    00:00:01  |   |       \_ ss_local
 125239 pts/0    00:00:01  |   |       \_ ss_local
 125253 pts/0    00:00:01  |   |       \_ ss_local
 125267 pts/0    00:00:01  |   |       \_ ss_local
 125281 pts/0    00:00:01  |   |       \_ ss_local
 125293 pts/0    00:00:01  |   |       \_ ss_local
 125307 pts/0    00:00:01  |   |       \_ ss_local
 125319 pts/0    00:00:01  |   |       \_ ss_local
 125336 pts/0    00:00:01  |   |       \_ ss_local
 125353 pts/0    00:00:01  |   |       \_ ss_local
 125368 pts/0    00:00:01  |   |       \_ ss_local
 125384 pts/0    00:00:01  |   |       \_ ss_local
 125401 pts/0    00:00:01  |   |       \_ ss_local
 125416 pts/0    00:00:01  |   |       \_ ss_local
 125431 pts/0    00:00:01  |   |       \_ ss_local
 125445 pts/0    00:00:01  |   |       \_ ss_local
 125461 pts/0    00:00:01  |   |       \_ ss_local
 125475 pts/0    00:00:01  |   |       \_ ss_local
 125489 pts/0    00:00:01  |   |       \_ ss_local
 125504 pts/0    00:00:01  |   |       \_ ss_local
 125519 pts/0    00:00:01  |   |       \_ ss_local
 125531 pts/0    00:00:01  |   |       \_ ss_local
 125545 pts/0    00:00:01  |   |       \_ ss_local
 125559 pts/0    00:00:01  |   |       \_ ss_local
 125573 pts/0    00:00:01  |   |       \_ ss_local
 125587 pts/0    00:00:01  |   |       \_ ss_local
 125601 pts/0    00:00:01  |   |       \_ ss_local
 125618 pts/0    00:00:01  |   |       \_ ss_local
 125632 pts/0    00:00:01  |   |       \_ ss_local
 125646 pts/0    00:00:01  |   |       \_ ss_local
 125662 pts/0    00:00:02  |   |       \_ ss_local
 125678 pts/0    00:00:01  |   |       \_ ss_local
 125694 pts/0    00:00:02  |   |       \_ ss_local
 125710 pts/0    00:00:01  |   |       \_ ss_local
 125724 pts/0    00:00:02  |   |       \_ ss_local
 125740 pts/0    00:00:01  |   |       \_ ss_local
 125754 pts/0    00:00:01  |   |       \_ ss_local
 125768 pts/0    00:00:01  |   |       \_ ss_local
 125782 pts/0    00:00:01  |   |       \_ ss_local
 125796 pts/0    00:00:01  |   |       \_ ss_local
 125808 pts/0    00:00:01  |   |       \_ ss_local
 125822 pts/0    00:00:01  |   |       \_ ss_local
 125838 pts/0    00:00:01  |   |       \_ ss_local
 125852 pts/0    00:00:01  |   |       \_ ss_local
 125868 pts/0    00:00:01  |   |       \_ ss_local
 125883 pts/0    00:00:01  |   |       \_ ss_local
 125902 pts/0    00:00:01  |   |       \_ ss_local
 125918 pts/0    00:00:01  |   |       \_ ss_local
 125934 pts/0    00:00:01  |   |       \_ ss_local
 125948 pts/0    00:00:01  |   |       \_ ss_local
 125964 pts/0    00:00:01  |   |       \_ ss_local
 125980 pts/0    00:00:01  |   |       \_ ss_local
 125996 pts/0    00:00:01  |   |       \_ ss_local
 126012 pts/0    00:00:01  |   |       \_ ss_local
 126026 pts/0    00:00:01  |   |       \_ ss_local
 126042 pts/0    00:00:01  |   |       \_ ss_local
 126056 pts/0    00:00:01  |   |       \_ ss_local
 126070 pts/0    00:00:01  |   |       \_ ss_local
 126086 pts/0    00:00:01  |   |       \_ ss_local
 126102 pts/0    00:00:01  |   |       \_ ss_local
 126118 pts/0    00:00:01  |   |       \_ ss_local
 126132 pts/0    00:00:01  |   |       \_ ss_local
 126146 pts/0    00:00:01  |   |       \_ ss_local
 126160 pts/0    00:00:01  |   |       \_ ss_local
 126174 pts/0    00:00:01  |   |       \_ ss_local
 126188 pts/0    00:00:01  |   |       \_ ss_local
 126202 pts/0    00:00:01  |   |       \_ ss_local
 126214 pts/0    00:00:01  |   |       \_ ss_local
 126228 pts/0    00:00:01  |   |       \_ ss_local
 126242 pts/0    00:00:01  |   |       \_ ss_local
 126256 pts/0    00:00:01  |   |       \_ ss_local
 126271 pts/0    00:00:01  |   |       \_ ss_local
 126284 pts/0    00:00:01  |   |       \_ ss_local
 126300 pts/0    00:00:01  |   |       \_ ss_local
 126314 pts/0    00:00:01  |   |       \_ ss_local
 126326 pts/0    00:00:01  |   |       \_ ss_local
 126340 pts/0    00:00:05  |   |       \_ ss_local
 126354 pts/0    00:00:01  |   |       \_ ss_local
 126368 pts/0    00:00:01  |   |       \_ ss_local
 126382 pts/0    00:00:01  |   |       \_ ss_local
 126396 pts/0    00:00:01  |   |       \_ ss_local
 126410 pts/0    00:00:01  |   |       \_ ss_local
 126569 pts/0    00:00:00  |   |       \_ sudo
 126588 pts/0    00:17:34  |   |       |   \_ haproxy
 126570 pts/0    00:00:00  |   |       \_ bash
 126692 pts/0    00:00:03  |   |       |   \_ tor
 126571 pts/0    00:00:00  |   |       \_ bash
 126830 pts/0    00:00:00  |   |       |   \_ tinyproxy
1590742 pts/0    00:00:00  |   |       \_ sleep
 444846 pts/1    00:00:00  |   \_ bash
 593591 pts/2    00:00:00  |   \_ bash
 596801 pts/2    00:00:33  |   |   \_ shutter
1276649 pts/3    00:00:00  |   \_ bash
2096511 pts/4    00:00:00  |   \_ bash
2237963 pts/5    00:00:00  |   \_ bash
 900040 pts/6    00:00:02  |   \_ bash
1591644 pts/6    00:00:00  |       \_ ps
 417567 ?        00:01:05  \_ tracker-miner-f
4051370 ?        00:00:20  \_ nautilus
2272722 ?        00:00:00  \_ gnome-calendar
2272975 ?        00:00:00  \_ gpg-agent
2375113 ?        00:00:00  \_ sd_espeak-ng
2375139 ?        00:00:00  \_ sd_dummy
2375149 ?        00:00:00  \_ sd_generic
2375159 ?        00:00:00  \_ speech-dispatch
1512007 ?        00:01:44  \_ tracker-store
   5150 ?        00:00:33 dockerd
  48003 tty2     00:00:54 dnsproxy
  48005 tty2     00:00:04 dnsproxy
  48936 ?        00:00:02 dnsmasq
  49163 ?        00:00:00 systemd-resolve
  49643 ?        00:00:00 systemd-network
  54123 ?        00:00:00 ssh-agent
1571651 ?        00:00:00 packagekitd


-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

> werner@X10DAi:~$ ps -e --forest [...]

OK, check out gnome-terminal and GSD (Gnome Settings Daemon),
I couldn't identify the window manager tho. The default for
Ubuntu is Compiz.

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

[-- Attachment #1: Type: text/plain, Size: 705 bytes --]

On Sun, Aug 1, 2021 at 3:15 PM Emanuel Berg via Users list for the GNU
Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> > werner@X10DAi:~$ ps -e --forest [...]
>
> OK, check out gnome-terminal and GSD (Gnome Settings Daemon),
> I couldn't identify the window manager tho. The default for
> Ubuntu is Compiz.

Strange. I checked both the terminal and system keyboard shortcuts
settings, and still can't the corresponding definition which using
`C-M-s'.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

[-- Attachment #2: system-settings.png --]
[-- Type: image/png, Size: 131735 bytes --]

[-- Attachment #3: terminal-settings.png --]
[-- Type: image/png, Size: 71861 bytes --]

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Sun, Aug 1, 2021 at 3:57 PM Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
>
> On Sun, Aug 1, 2021 at 3:15 PM Emanuel Berg via Users list for the GNU
> Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> >
> > Hongyi Zhao wrote:
> >
> > > werner@X10DAi:~$ ps -e --forest [...]
> >
> > OK, check out gnome-terminal and GSD (Gnome Settings Daemon),
> > I couldn't identify the window manager tho. The default for
> > Ubuntu is Compiz.
>
> Strange. I checked both the terminal and system keyboard shortcuts
> settings, and still can't the corresponding definition which using
> `C-M-s'.

By unchecking the `Enable shortcuts' option on GNOME Terminal's
shortcuts panel, I can confirm `C-h k C-M-s RET' says the following:

C-M-s runs the command isearch-forward-regexp

Regards,
HY

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> But, BTW, I haven't done any configuration for gnus [1], but instead,
> I noticed the following `custom-set-variables' setting in my
> `~/.emacs.d/init.el':
>
> '(send-mail-function 'mailclient-send-it)
>
> If I want to use gnus to do the job through my Gmail account, what
> adjustments should I make?

If you don't get satisfying answers here, emacs.gnus.user and
emacs.gnus.general are Gnus specific groups to ask.

I am using Gnus.  M-x emacs-bug-report still doesn't start Gnus, I get a
buffer in message-mode instead.  You get the same when starting to
compose a new message from within Gnus.

You might want to start with one of the tasks (1) sending Email from
Emacs and (2) reading Email and News using Gnus.

For sending mail, AFAIR you need a sendmail program installed (or did
this change...? I don't reacall).  I installed esmtp since it's easy to
configure it.  I have a ~/.authinfo.gpg with servers, usernames and
passwords (including the smtp-Server I use for sending mails), and, I
guess, that's already all I config needed outside Emacs.

Then some basic setup like

(setq-default
 send-mail-function #'smtpmail-send-it
 mail-user-agent 'gnus-user-agent
 user-mail-address ... )

You will want to store Email addresses somewhere, there are multiple
solutions for that (EBDB, BBDB, Org, probably more).

For basic stuff, i.e. unless you want to use Gnus more or less as your
one and only mail reader, you can also choose a more lightweight
approach inside Emacs, instead of Gnus.

If you do want to use Gnus, there is some more setup involved, but it is
not harder to setup than other mail readers if you are used to Emacs.

There is a cool gnus-mock called package for testing purposes available
in Gnu Elpa that always starts with the same basic but functional setup,
if you just want to try out how it looks like, and try out first
settings.

Gnus then has its own `gnus-init-file', that's where your Gnus specific
settings would go.

Some variables you probably want to set:

#+begin_src emacs-lisp
(setq-default
 mail-sources '((file :path "/var/mail/my-user-name")) ;"system" mail
 gnus-message-archive-method ;where stuff is saved
 '(nnml "archive"
	(nnml-directory "~/Mail/archive/")
	(nnml-active-file "~/Mail/archive/active")
	(nnml-newsgroups-file "~/Mail/archive/newsgroups"))
 gnus-message-archive-group "sent" ;your sent mails go there
 mail-archive-file-name nil ;have forgotten why I have this
 gnus-article-save-directory (expand-file-name "~/Mail/archive/read/")
 nntp-authinfo-file          (expand-file-name "~/.authinfo.gpg"); see above
 message-directory           (expand-file-name "~/Mail/")

 epa-file-cache-passphrase-for-symmetric-encryption t

 gnus-secondary-select-methods
 '((nnimap "Michael_Heerdegen@web.de"
	   (nnimap-address "imap.web.de"))
   (nntp "Gmane" (nntp-address "news.gmane.io"))
   (nntp "news.gnus.org"))
 gnus-select-method (car gnus-secondary-select-methods)

 gnus-default-article-saver #'gnus-summary-save-in-folder

 gnus-blocked-images #'gnus-block-private-groups)
#+end_src

Could be that there are some redundancies, and you want to use your own
Email addresses (I guess).

That's the answer to the question what you would have to do.  There are
probably lots of good "How to get started" manuals out there, and the
Gnus manual itself is written in a nice and funny way, don't hesitate to
read at length.


Michael.

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Mon, Aug 2, 2021 at 7:59 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > But, BTW, I haven't done any configuration for gnus [1], but instead,
> > I noticed the following `custom-set-variables' setting in my
> > `~/.emacs.d/init.el':
> >
> > '(send-mail-function 'mailclient-send-it)
> >
> > If I want to use gnus to do the job through my Gmail account, what
> > adjustments should I make?
>
> If you don't get satisfying answers here, emacs.gnus.user and
> emacs.gnus.general are Gnus specific groups to ask.

Are these newsgroups or mailing lists? I can't find them on:
<https://www.gnus.org/resources.html>.

> I am using Gnus.  M-x emacs-bug-report still doesn't start Gnus, I get a
> buffer in message-mode instead.  You get the same when starting to
> compose a new message from within Gnus.
>
> You might want to start with one of the tasks (1) sending Email from
> Emacs and (2) reading Email and News using Gnus.
>
> For sending mail, AFAIR you need a sendmail program installed (or did
> this change...? I don't reacall).  I installed esmtp since it's easy to
> configure it.  I have a ~/.authinfo.gpg with servers, usernames and
> passwords (including the smtp-Server I use for sending mails), and, I
> guess, that's already all I config needed outside Emacs.
>
> Then some basic setup like
>
> (setq-default
>  send-mail-function #'smtpmail-send-it
>  mail-user-agent 'gnus-user-agent
>  user-mail-address ... )
>
> You will want to store Email addresses somewhere, there are multiple
> solutions for that (EBDB, BBDB, Org, probably more).
>
> For basic stuff, i.e. unless you want to use Gnus more or less as your
> one and only mail reader, you can also choose a more lightweight
> approach inside Emacs, instead of Gnus.
>
> If you do want to use Gnus, there is some more setup involved, but it is
> not harder to setup than other mail readers if you are used to Emacs.
>
> There is a cool gnus-mock called package for testing purposes available
> in Gnu Elpa that always starts with the same basic but functional setup,
> if you just want to try out how it looks like, and try out first
> settings.

Thank you for letting know this interesting tool [1].

[1] https://elpa.gnu.org/packages/gnus-mock.html

> Gnus then has its own `gnus-init-file', that's where your Gnus specific
> settings would go.
>
> Some variables you probably want to set:
>
> #+begin_src emacs-lisp
> (setq-default
>  mail-sources '((file :path "/var/mail/my-user-name")) ;"system" mail
>  gnus-message-archive-method ;where stuff is saved
>  '(nnml "archive"
>         (nnml-directory "~/Mail/archive/")
>         (nnml-active-file "~/Mail/archive/active")
>         (nnml-newsgroups-file "~/Mail/archive/newsgroups"))
>  gnus-message-archive-group "sent" ;your sent mails go there
>  mail-archive-file-name nil ;have forgotten why I have this
>  gnus-article-save-directory (expand-file-name "~/Mail/archive/read/")
>  nntp-authinfo-file          (expand-file-name "~/.authinfo.gpg"); see above
>  message-directory           (expand-file-name "~/Mail/")
>
>  epa-file-cache-passphrase-for-symmetric-encryption t
>
>  gnus-secondary-select-methods
>  '((nnimap "Michael_Heerdegen@web.de"
>            (nnimap-address "imap.web.de"))
>    (nntp "Gmane" (nntp-address "news.gmane.io"))
>    (nntp "news.gnus.org"))
>  gnus-select-method (car gnus-secondary-select-methods)
>
>  gnus-default-article-saver #'gnus-summary-save-in-folder
>
>  gnus-blocked-images #'gnus-block-private-groups)
> #+end_src
>
> Could be that there are some redundancies, and you want to use your own
> Email addresses (I guess).
>
> That's the answer to the question what you would have to do.  There are
> probably lots of good "How to get started" manuals out there, and the
> Gnus manual itself is written in a nice and funny way, don't hesitate to
> read at length.

Thank you very much again for your helpful and exhaustive explanations.

> Michael.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Michael Heerdegen wrote:

> If you don't get satisfying answers here, emacs.gnus.user
> and emacs.gnus.general are Gnus specific groups to ask.

gmane.emacs.gnus.general (or ding@gnus.org)
gmane.emacs.gnus.user    (or info-gnus-english@gnu.org)

gmane.emacs.gnus.general has 86 407 posts right now while
gmane.emacs.gnus.user has 19 465, so better to use
gmane.emacs.gnus.general, perhaps.

> I am using Gnus. M-x emacs-bug-report still doesn't start
> Gnus, I get a buffer in message-mode instead. You get the
> same when starting to compose a new message from
> within Gnus.

Gnus has its own report system as well,

  M-x gnus-bug RET

Here is my Gnus stuff:

  https://dataswamp.org/~incal/emacs-init/gnus/

"Gnus is to Emacs users,
what Emacs is to computer users."

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

> Are these newsgroups or mailing lists? I can't find them on:
> <https://www.gnus.org/resources.html>.

They are mailing lists, ding@gnus.org and
info-gnus-english@gnu.org, however with Gnus and in particular
the mailing-list-to-NNTP gateway Gmane, one can read and
interact with them, and do a lot of other stuff, with the
convenience of the newsgroup organization and interface. (In
this case, as said, as gmane.emacs.gnus.general and
gmane.emacs.gnus.user, respectively.)

You can do old, real Usenet (from for example nntp.aioe.org) -
not sure if that's a good idea as quality hasn't exactly
picked up, but it's possible nonetheless - you can do mailing
lists, as exemplified above, from news.gmane.io - you can do
mail (several backends possible, I recommend nnml) - even read
blogs from gwene.org - all with the same, great interface.

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> Are these newsgroups or mailing lists? I can't find them on:
> <https://www.gnus.org/resources.html>.

Ok, my mistake, I was confused by the gmane group name.  This should be
correct:

Mailing list: info-gnus-english@gnu.org
Group:        gnu.emacs.gnus or gmane.emacs.gnus.user

I hope these correspond to each other.  I also found this:

  https://gnus.org/resources.html

but I don't recall whether these "ding" addresses are still valid or if
they were replaced with other names (or just aliases?).

  (info "(gnus) Gnus Development")

has some information which should be up to date and mentions the names I
have listed at the top.

Michael.

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Michael Heerdegen wrote:

> Mailing list: info-gnus-english@gnu.org
> Group:        gnu.emacs.gnus or gmane.emacs.gnus.user

gnu.emacs.gnus on Usenet (nntp.aioe.org) has only 9 posts.

It is better to use gmane.emacs.gnus.general (news.gmane.io),
that group doesn't even seem to be on Usenet so all the more
reason to use Gmane for that :)

(Here is another advantage with Gnus BTW, the possibility to
search servers for mailing lists/newsgroups/blogs (RSS feeds)
just as you'd search any Emacs buffer.)

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

> Gnus has its own report system as well,
>
>   M-x gnus-bug RET

I always thought that's for bugs about Gnus, but seems I was wrong.

The command definition shows it's the same as `report-emacs-bug' plus an
added "X-Debbugs-Package" header.  It doesn't seem to provide any extra
comfort - right?

Michael.

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Mon, Aug 2, 2021 at 9:16 AM Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Hongyi Zhao <hongyi.zhao@gmail.com> writes:
>
> > Are these newsgroups or mailing lists? I can't find them on:
> > <https://www.gnus.org/resources.html>.
>
> Ok, my mistake, I was confused by the gmane group name.  This should be
> correct:
>
> Mailing list: info-gnus-english@gnu.org
> Group:        gnu.emacs.gnus or gmane.emacs.gnus.user
>
> I hope these correspond to each other.  I also found this:
>
>   https://gnus.org/resources.html
>
> but I don't recall whether these "ding" addresses are still valid or if
> they were replaced with other names (or just aliases?).
>
>   (info "(gnus) Gnus Development")

If you try (info "(gnus) History"), Emacs will direct you to an info
page, which says the following:

;;;
If you want to investigate the person responsible for this outrage,
you can point your (feh!)  web browser to <https://quimby.gnus.org/>.
This is also the primary distribution point for the new and spiffy
versions of Gnus, and is known as The Site That Destroys Newsrcs And
Drives People Mad.
;;;

Then I find the following info on
<https://quimby.gnus.org/gnus/distribution.html>:

;;;
Downloading the development Gnus version from git

The server uses packed refs. Make sure your version of Git can handle
them (1.7.0.4 and later definitely do).

Public access

git clone http://git.gnus.org/gnus.git
;;;

I tried with the above git clone command, but failed as shown below:

$ git clone http://git.gnus.org/gnus.git
Cloning into 'gnus'...
fatal: unable to access 'http://git.gnus.org/gnus.git/': Empty reply from server


In short, the gnus related stuff in Emacs looks a bit confusing.

> has some information which should be up to date and mentions the names I
> have listed at the top.
>
> Michael.

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Michael Heerdegen wrote:

>> Gnus has its own report system as well,
>>
>>   M-x gnus-bug RET
>
> I always thought that's for bugs about Gnus, but seems
> I was wrong.

Why?

"If you find a bug in Gnus, you can report it with the
M-x gnus-bug command."
<http://kirste.userpage.fu-berlin.de/chemnet/use/info/gnus/gnus_10.html>
or (info "(gnus) Troubleshooting")

> The command definition shows it's the same as
> `report-emacs-bug' plus an added "X-Debbugs-Package" header.
> It doesn't seem to provide any extra comfort - right?

Maybe it branches somewhere to bugs@gnus.org because of that...

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Hongyi Zhao <hongyi.zhao@gmail.com> writes:

Ok, let's CC Lars, maybe he wants to remove that texts (following
citations) from the manual and/or his page, or he has something else to
say.

> (info "(gnus) History")
> [...]
> If you want to investigate the person responsible for this outrage,
> you can point your (feh!)  web browser to <https://quimby.gnus.org/>.
> This is also the primary distribution point for the new and spiffy
> versions of Gnus, and is known as The Site That Destroys Newsrcs And
> Drives People Mad.
> [...]
> <https://quimby.gnus.org/gnus/distribution.html>

> $ git clone http://git.gnus.org/gnus.git
> Cloning into 'gnus'...
> fatal: unable to access 'http://git.gnus.org/gnus.git/': Empty reply
> from server

Maybe this information is outdated?  I guess development has just moved
to the Emacs repo when Emacs switched to Git and Gnus has been mostly
"done".

Michael.

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

>> but I don't recall whether these "ding" addresses are still
>> valid or if they were replaced with other names (or just
>> aliases?).
>>
>>   (info "(gnus) Gnus Development")

ding@gnus.org is valid, ding = ding is not GNUS, a proposed
joke acronym (recursive backronym) that didn't take, maybe
because Gnus is already such a good and interesting name.

> Downloading the development Gnus version from git

Gnus is part of vanilla Emacs so no need to download/install
it separately.

E.g., my Emacs, namely (C-u M-x emacs-version RET)

  GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.5, cairo version 1.16.0) of 2020-10-23

has Gnus version (C-u M-x gnus-version RET)

  Gnus v5.13

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Michael Heerdegen wrote:

> Maybe this information is outdated? I guess development has
> just moved to the Emacs repo when Emacs switched to Git and
> Gnus has been mostly "done".

People work on Gnus :)

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Mon, Aug 2, 2021 at 10:25 AM Emanuel Berg via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> >> but I don't recall whether these "ding" addresses are still
> >> valid or if they were replaced with other names (or just
> >> aliases?).
> >>
> >>   (info "(gnus) Gnus Development")
>
> ding@gnus.org is valid, ding = ding is not GNUS, a proposed
> joke acronym (recursive backronym) that didn't take, maybe
> because Gnus is already such a good and interesting name.
>
> > Downloading the development Gnus version from git
>
> Gnus is part of vanilla Emacs so no need to download/install
> it separately.
>
> E.g., my Emacs, namely (C-u M-x emacs-version RET)
>
>   GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.5, cairo version 1.16.0) of 2020-10-23

With the command you suggested above, I only get the following information:

emacs-build-number is a variable defined in ‘version.el’.

Its value is 1


> has Gnus version (C-u M-x gnus-version RET)

This function, `gnus-version', doesn't exist on my side at all.


>   Gnus v5.13
>
> --
> underground experts united
> https://dataswamp.org/~incal
>
>

Best
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

> emacs-build-number is a variable defined in ‘version.el’.
>
> Its value is 1
>
>> has Gnus version (C-u M-x gnus-version RET)
>
> This function, `gnus-version', doesn't exist on my side
> at all.

Hm ... maybe it wasn't included in Emacs 1?

Please use these commands to install Emacs from source.

Then do `emacs-version' (or 'emacs --version' in the
shell). And look for `gnus-version'.

It's there :)

#! /bin/zsh
#
# this file:
#   http://user.it.uu.se/~embe8573/conf/.zsh/install-emacs
#   https://dataswamp.org/~incal/conf/.zsh/install-emacs

export EMACS_SOURCE=https://github.com/mirrors/emacs.git

prepare-emacs-install () {
    local ver=${1:-$(emacs --version | head -n 1 | awk '{print $3}' | cut -d '.' -f 1)}
    local emacs_pack=emacs${ver}
    sudo apt-get update > /dev/null
    sudo apt-get install build-essential
    sudo apt-get build-dep $emacs_pack
}

reset-emacs-source () {
    git reset --hard
    git clean -xdf
    git pull $EMACS_SOURCE
}

get-emacs-source () {
    git clone $EMACS_SOURCE
}

# $ ./autogen.sh
# $ ./configure --with-modules
# $ make
# $ sudo make install

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Michael Heerdegen]

Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

> Hongyi Zhao wrote:
>
> > emacs-build-number is a variable defined in ‘version.el’.
> >
> > Its value is 1
> >
> >> has Gnus version (C-u M-x gnus-version RET)
> >
> > This function, `gnus-version', doesn't exist on my side
> > at all.
>
> Hm ... maybe it wasn't included in Emacs 1?
>
> Please use these commands to install Emacs from source.

Maybe he just did something wrong.  The build number is also available
in the prefilled buffer you get from M-x report-emacs-bug, you can look
there.

`emacs-version' is a normal function (and command, and a
variable)... nothing special about it.  Unless your build is really
broken, but let's not assume that for now.

> Then do `emacs-version' (or 'emacs --version' in the
> shell). And look for `gnus-version'.

Note that gnus-version is not autoloaded.  One needs to load gnus before
it is available.

And I have forgotten what the purpose was to look at it.

Michael.

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Mon, Aug 2, 2021 at 11:29 AM Emanuel Berg via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> > emacs-build-number is a variable defined in ‘version.el’.
> >
> > Its value is 1
> >
> >> has Gnus version (C-u M-x gnus-version RET)
> >
> > This function, `gnus-version', doesn't exist on my side
> > at all.
>
> Hm ... maybe it wasn't included in Emacs 1?
>
> Please use these commands to install Emacs from source.
>
> Then do `emacs-version' (or 'emacs --version' in the
> shell). And look for `gnus-version'.
>
> It's there :)
>
> #! /bin/zsh
> #
> # this file:
> #   http://user.it.uu.se/~embe8573/conf/.zsh/install-emacs
> #   https://dataswamp.org/~incal/conf/.zsh/install-emacs
>
> export EMACS_SOURCE=https://github.com/mirrors/emacs.git

I use the real upstream repo, instead of the mirror, as shown below:

https://git.savannah.gnu.org/git/emacs.git

According to my experience, the mirror will lag behind the upstream by
several days in commits.

> prepare-emacs-install () {
>     local ver=${1:-$(emacs --version | head -n 1 | awk '{print $3}' | cut -d '.' -f 1)}
>     local emacs_pack=emacs${ver}
>     sudo apt-get update > /dev/null
>     sudo apt-get install build-essential
>     sudo apt-get build-dep $emacs_pack
> }
>
> reset-emacs-source () {
>     git reset --hard
>     git clean -xdf
>     git pull $EMACS_SOURCE
> }
>
> get-emacs-source () {
>     git clone $EMACS_SOURCE
> }
>
> # $ ./autogen.sh
> # $ ./configure --with-modules

This is the default behavior, so it is needless if you want this feature.

> # $ make
> # $ sudo make install
>
> --
> underground experts united
> https://dataswamp.org/~incal
>
>


-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Michael Heerdegen wrote:

>> Then do `emacs-version' (or 'emacs --version' in the
>> shell). And look for `gnus-version'.
>
> Note that gnus-version is not autoloaded. One needs to load
> gnus before it is available.
>
> And I have forgotten what the purpose was to look at it.

:) Same.

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

>> export EMACS_SOURCE=https://github.com/mirrors/emacs.git
>
> I use the real upstream repo, instead of the mirror, as
> shown below:
>
> https://git.savannah.gnu.org/git/emacs.git
>
> According to my experience, the mirror will lag behind the
> upstream by several days in commits.

OK, let's install it from there... 1s

-- 
underground experts united
https://dataswamp.org/~incal

gnutls and `erc-tls' (was: Re: [External] : Re: Package cl is deprecated)

[Emanuel Berg via Users list for the GNU Emacs text editor]

>>> export EMACS_SOURCE=https://github.com/mirrors/emacs.git
>>
>> I use the real upstream repo, instead of the mirror, as
>> shown below:
>>
>> https://git.savannah.gnu.org/git/emacs.git
>>
>> According to my experience, the mirror will lag behind the
>> upstream by several days in commits.
>
> OK, let's install it from there... 1s

OK, so now I have, instead of Emacs 28.0.5 build 1, have

  GNU Emacs 28.0.50 (build 2, x86_64-pc-linux-gnu) of
  2021-08-02

`emacs-version' is here, so is `gnus-version'

  Gnus v5.13

But during installation, at configuration it complained that
gnutls wasn't available. I installed the \*gnutls\* packs from
the Debian repos, and the configuration didn't complain.
The rest of the installation went fine.

But now, it seems I can't connect to IRC! Failed on two
servers, it doesn't get by the "Opening connection.." stage.

I do (did) that with `erc-tls', so it makes sense it
is related.

Ideas?

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Stefan Monnier via Users list for the GNU Emacs text editor]

> https://git.savannah.gnu.org/git/emacs.git

Note that

    git://git.sv.gnu.org/emacs.git

is significantly faster in my experience (because it uses the "smart"
Git protocol, whereas the http/https server running on Savannah is
apparently not configured to let Git use that "smart" protocol).


        Stefan

Re: gnutls and `erc-tls' (was: Re: [External] : Re: Package cl is deprecated)

[Emanuel Berg via Users list for the GNU Emacs text editor]

> But during installation, at configuration it complained that
> gnutls wasn't available. I installed the \*gnutls\* packs
> from the Debian repos, and the configuration didn't
> complain. The rest of the installation went fine.
>
> But now, it seems I can't connect to IRC! Failed on two
> servers, it doesn't get by the "Opening connection.." stage.
>
> I do (did) that with `erc-tls', so it makes sense it
> is related.

I solved the above issue by setting the `erc-port' to the
SSL/TLS customary 6697, and now it works - so the whole thing
probably wasn't related to the installation, it just looked
that way.

  (setq erc-port 6697)

With these commands there is no trouble whatsoever getting and
installing Emacs, just like last time - I just had to change
the commands a bit :)

#! /bin/zsh
#
# this file:
#   http://user.it.uu.se/~embe8573/conf/.zsh/install-emacs
#   https://dataswamp.org/~incal/conf/.zsh/install-emacs

local EMACS_SRC=https://git.savannah.gnu.org/git/emacs.git

emacs-install-prepare () {
    sudo apt-get update > /dev/null
    sudo apt-get install build-essential
    sudo apt-get build-dep emacs
}

emacs-src-reset () {
    git reset --hard
    git clean -xdf
    git pull $EMACS_SRC
}

emacs-src-get () {
    git clone $EMACS_SRC
}

# $ ./autogen.sh
# $ ./configure --with-x-toolkit=no
# $ make
# $ sudo make install

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Tue, Aug 3, 2021 at 5:33 AM Stefan Monnier via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> > https://git.savannah.gnu.org/git/emacs.git
>
> Note that
>
>     git://git.sv.gnu.org/emacs.git
>
> is significantly faster in my experience (because it uses the "smart"
> Git protocol, whereas the http/https server running on Savannah is
> apparently not configured to let Git use that "smart" protocol).

Git's net transfer stack in itself is based on libcurl, regardless
what protocols are used on the user interface, OTOH, the internet is
complicated, and the overall network path and the performance may be
very different in different places. See my testings as shown below:

$ git clone  https://git.savannah.gnu.org/git/emacs.git
Cloning into 'emacs'...
remote: Counting objects: 942661, done.
remote: Compressing objects: 100% (166820/166820), done.
remote: Total 942661 (delta 775806), reused 941243 (delta 774565)
Receiving objects: 100% (942661/942661), 313.44 MiB | 9.37 MiB/s, done.
^Csolving deltas:   8% (62065/775806)

$ git clone git://git.sv.gnu.org/emacs.git
Cloning into 'emacs'...
remote: Counting objects: 942661, done.
remote: Compressing objects: 100% (166820/166820), done.
remote: Total 942661 (delta 775806), reused 941243 (delta 774565)
Receiving objects: 100% (942661/942661), 313.44 MiB | 9.22 MiB/s, done.
^Csolving deltas:  26% (201710/775806)


>         Stefan

Best regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Tue, Aug 3, 2021 at 3:55 AM Emanuel Berg via Users list for the GNU
Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> Hongyi Zhao wrote:
>
> >> export EMACS_SOURCE=https://github.com/mirrors/emacs.git
> >
> > I use the real upstream repo, instead of the mirror, as
> > shown below:
> >
> > https://git.savannah.gnu.org/git/emacs.git
> >
> > According to my experience, the mirror will lag behind the
> > upstream by several days in commits.
>
> OK, let's install it from there... 1s

What's the meaning of `1s'?

Regards
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > OK, let's install it from there... 1s
> What's the meaning of `1s'?

1 billion nanoseconds

Re: [External] : Re: Package cl is deprecated

[Hongyi Zhao]

On Tue, Aug 3, 2021 at 9:29 AM Drew Adams <drew.adams@oracle.com> wrote:
>
> > > OK, let's install it from there... 1s
> > What's the meaning of `1s'?
>
> 1 billion nanoseconds

Where or how is this derived or calculated?

Best
-- 
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province

RE: [External] : Re: Package cl is deprecated

[Drew Adams]

> > > > OK, let's install it from there... 1s
> > > What's the meaning of `1s'?
> >
> > 1 billion nanoseconds
> 
> Where or how is this derived or calculated?

https://en.wikipedia.org/wiki/Nanosecond

Re: [External] : Re: Package cl is deprecated

[Emanuel Berg via Users list for the GNU Emacs text editor]

Hongyi Zhao wrote:

>>>> OK, let's install it from there... 1s
>>> What's the meaning of `1s'?
>>
>> 1 billion nanoseconds
>
> Where or how is this derived or calculated?

Try 'units "1s" nanoseconds'.

-- 
underground experts united
https://dataswamp.org/~incal

Re: [External] : Re: Package cl is deprecated

[Stefan Monnier via Users list for the GNU Emacs text editor]

> $ git clone  https://git.savannah.gnu.org/git/emacs.git
> Cloning into 'emacs'...
> remote: Counting objects: 942661, done.
> remote: Compressing objects: 100% (166820/166820), done.
> remote: Total 942661 (delta 775806), reused 941243 (delta 774565)
> Receiving objects: 100% (942661/942661), 313.44 MiB | 9.37 MiB/s, done.
> ^Csolving deltas:   8% (62065/775806)
>
> $ git clone git://git.sv.gnu.org/emacs.git
> Cloning into 'emacs'...
> remote: Counting objects: 942661, done.
> remote: Compressing objects: 100% (166820/166820), done.
> remote: Total 942661 (delta 775806), reused 941243 (delta 774565)
> Receiving objects: 100% (942661/942661), 313.44 MiB | 9.22 MiB/s, done.
> ^Csolving deltas:  26% (201710/775806)

IIRC the main difference in speed was the time to get to "Receiving objects".
The bandwidth itself was not significantly affected.


        Stefan