From: Narendra Joshi <narendraj9@gmail.com>
To: Ergus <spacibba@aol.com>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Scroll on save
Date: Tue, 14 Jul 2020 18:13:54 +0200 [thread overview]
Message-ID: <87y2nmvzul.fsf@gmail.com> (raw)
In-Reply-To: <20200714103220.p4t357hedaujs67o@ergus> (Ergus's message of "Tue, 14 Jul 2020 12:32:20 +0200")
Ergus <spacibba@aol.com> writes:
The next thing that I would try is using the command `profiler-start`
just before saving the buffer and then `profiler-report` after saving
the buffer to narrow your search down to a couple of functions that
might be causing this. I am not sure if this would actually help but
worth trying.
> This is weird, because both hooks are nil. And the problem starts
> randomly after some time without apparent reason.
>
> On Tue, Jul 14, 2020 at 12:38:05AM +0200, Narendra Joshi wrote:
>>I would recommend that you check the values for after-save-hook and
>>before-save-hook.
>>
>>On Tue, 14 Jul 2020, 00:35 Ergus, <spacibba@aol.com> wrote:
>>
>>> Hi:
>>>
>>> Recently I have observed that when I save long files (C-x C-s) (either
>>> in a C file or Latex); for some reason emacs scrolls to some different
>>> place in the buffer. I am pretty sure that it should has to do with my
>>> config, but I don't know where to start looking for the problem.
>>>
>>> Does anyone has an idea or similar experience in the past? Any help to
>>> solve it will be fine.
>>>
>>> Thanks in advance,
>>> Ergus.
>>>
>>>
>>>
>
--
Narendra Joshi
next prev parent reply other threads:[~2020-07-14 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200713223521.jbjgmzyxxp2w45ot.ref@Ergus>
2020-07-13 22:35 ` Scroll on save Ergus
2020-07-13 22:38 ` Narendra Joshi
2020-07-13 22:39 ` Narendra Joshi
2020-07-14 10:32 ` Ergus
2020-07-14 16:13 ` Narendra Joshi [this message]
2020-07-13 23:00 ` Óscar Fuentes
2020-07-14 10:34 ` Ergus
2020-07-14 12:26 ` Tomas Nordin
2020-07-14 16:54 ` Dmitry Alexandrov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2nmvzul.fsf@gmail.com \
--to=narendraj9@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=spacibba@aol.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).