[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Indentation and gc
From: |
Eli Zaretskii |
Subject: |
Re: Indentation and gc |
Date: |
Sat, 11 Mar 2023 08:52:06 +0200 |
> Date: Fri, 10 Mar 2023 22:30:42 +0100
> From: Ergus <spacibba@aol.com>
>
> >> 2) IF it doesn't impact performance... Is it possible somehow to improve
> >> the gc message to have more useful information; or at least; to control
> >> the no-log in order to have some outputs in the *Message* buffer?
> >
> >How will a more detailed GC message help?
> >
>
> Hi,
>
> I explained wrongly. These were somehow two almost independent questions. The
> more detailed GC and having a logging alternative are useful for debugging
> purposes. Because (for example) I don't know exactly how many GC were
> executed during the indentation.
>
> So they are related but not directly.
I think I understood, but my question still stands: how will a more
detailed GC report help you in what you are trying to do?
You can see the kind of data GC returns in the doc string of
garbage-collect, and you can see that in action if you invoke
"M-x garbage-collect RET" by hand. Please tell how will this data
help you do what you want to do.
- Re: Indentation and gc, (continued)
- Re: Indentation and gc, Ihor Radchenko, 2023/03/13
- Re: Indentation and gc, Eli Zaretskii, 2023/03/13
- Re: Indentation and gc, Po Lu, 2023/03/11
- Re: Indentation and gc, Eli Zaretskii, 2023/03/11
- Re: Indentation and gc, Ihor Radchenko, 2023/03/11
- Re: Indentation and gc, Eli Zaretskii, 2023/03/11
Re: Indentation and gc, Eli Zaretskii, 2023/03/10
Re: Indentation and gc, Jean Louis, 2023/03/21