On Thu, Sep 29, 2022 at 4:19 PM Ihor Radchenko wrote:
> Or you can bisect the config to hunt for less obvious issues using
> https://github.com/Malabarba/elisp-bug-hunter
>
I'm preparing a new machine right now, so I will plug into the emacs
configuration one bit ata time and see when the problem
Luca Ferrari writes:
>> Do you have any flyspell-related configuration in your config?
>
> I have:
> (flyspell-mode +1)
> (global-flycheck-mode +1)
Hmm. Can you try the development version of Org?
If you are just using a bare flyspell-mode, it generally gets slow on
large Org files. We have made
On Thu, Sep 29, 2022 at 4:27 AM Ihor Radchenko wrote:
>
> Luca Ferrari writes:
>
> >> I'm trying to understand what could be eating all the cpu.
> >>
> >
> > So far, turning off flyspell-mode makes Emacs work fine again. Strange...
>
> Do you have any flyspell-related configuration in your config
Luca Ferrari writes:
>> I'm trying to understand what could be eating all the cpu.
>>
>
> So far, turning off flyspell-mode makes Emacs work fine again. Strange...
Do you have any flyspell-related configuration in your config?
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode
On Wed, Sep 28, 2022 at 3:15 PM Ihor Radchenko wrote:
> I have not idea except that you may have something really strange in
> your config.
I'm trying to understand what could be eating all the cpu.
> What if you open the file in a clean Emacs instance? See
> https://orgmode.org/manual/Feedback.
Luca Ferrari writes:
> No, there is no buffer named cpu nor memory nor something alike in the
> buffer list.
I have not idea except that you may have something really strange in
your config.
> Besides, I'm now more able to reproduce the original issue: I open one
> of my perl-based org files, a
On Wed, Sep 28, 2022 at 4:15 PM Luca Ferrari wrote:
>
> On Wed, Sep 28, 2022 at 3:15 PM Ihor Radchenko wrote:
> > I have not idea except that you may have something really strange in
> > your config.
>
> I'm trying to understand what could be eating all the cpu.
>
So far, turning off flyspell-mo
On Tue, Sep 27, 2022 at 3:22 PM Ihor Radchenko wrote:
>
> This is strange.
> Did nothing happen after M-x profiler-report?
> Can you try again and check if *CPU-Profiler-Report ...* buffer exists
> in Emacs (... will be current date and time)?
No, there is no buffer named cpu nor memory nor somet
Luca Ferrari writes:
> On Mon, Sep 26, 2022 at 5:16 PM Ihor Radchenko wrote:
>> I think you tried to use M-x profiler-stop instead of M-x profiler-report
>> M-x profiler-report show yield a new buffer displayed the profiler tree.
>> M-x profiler-write-profile will work from inside that buffer.
>
On Mon, Sep 26, 2022 at 5:16 PM Ihor Radchenko wrote:
> I think you tried to use M-x profiler-stop instead of M-x profiler-report
> M-x profiler-report show yield a new buffer displayed the profiler tree.
> M-x profiler-write-profile will work from inside that buffer.
I was careful to do the step
Luca Ferrari writes:
> On Mon, Sep 26, 2022 at 6:41 AM Ihor Radchenko wrote:
>> Thanks for reporting!
>> May you
>> 1. M-x profiler-start cpu
>> 2. Move/paste/edit your source block
>> 3. M-x profiler-report
>> 4. M-x profiler-report-write-profile and share the resulting file here
>
> Apparen
On Mon, Sep 26, 2022 at 6:41 AM Ihor Radchenko wrote:
> Thanks for reporting!
> May you
> 1. M-x profiler-start cpu
> 2. Move/paste/edit your source block
> 3. M-x profiler-report
> 4. M-x profiler-report-write-profile and share the resulting file here
Apparently I'm not able to get the profil
Luca Ferrari writes:
> Hi all,
> I'm having issues in my org files whenever I insert a new source block
> (perl if that matters) with "#+begin_src perl" Emacs becomes really
> slow.
> I can move, paste, edit within the source block (in the same org
> buffer, not an external window) but at a very
13 matches
Mail list logo
