From: Marcin Borkowski <mbork@mbork.pl>
To: Lajos Bodnar <bodnarlajoska@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: magit-status is slow
Date: Mon, 11 Jun 2018 18:02:18 +0200 [thread overview]
Message-ID: <87a7s1gvlh.fsf@mbork.pl> (raw)
In-Reply-To: <CAPibjnm8MwWJw+EPDkZ=-nodoWtva1aYTvj1Fw0jUPrpon8oJw@mail.gmail.com>
On 2018-06-11, at 17:10, Lajos Bodnar <bodnarlajoska@gmail.com> wrote:
> Hi,
> I have 200 files after refactoring and the magit is too slow.
> I found that the diff is slow because the magit-status create diffing view
> every modified files.
> How can I reach that the magit-state create diffing view just when I work
> with these files when I use the tab key to watch what the change was.
>
> Or any ideas ?
It's a long shot, but do you have something like
(setq magit-diff-refine-hunk t)
in your init.el? If yes, try disabling this. (You can also press
D t in magit fir that.)
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2018-06-11 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 15:10 magit-status is slow Lajos Bodnar
2018-06-11 16:02 ` Marcin Borkowski [this message]
2018-06-12 9:06 ` Lajos Bodnar
2018-06-15 4:53 ` Marcin Borkowski
2018-06-19 19:51 ` Lajos Bodnar
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=87a7s1gvlh.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=bodnarlajoska@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).