[kate] [Bug 424073] Slow start on automounted home

2020-07-11 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=424073

--- Comment #5 from Christoph Cullmann  ---
Sorry that this makes it not that usable for you.

On the other side, a lot of tools do exactly that to e.g. discover their
projects, git will do just the same, just call some git status somewhere, it
will search upwards like Kate does to detect if it is inside a project, up to
the / (for .git/.git/HEAD/HEAD..)

stat("/home/cullmann/tmp", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat("/home/cullmann/tmp/.git", 0x7fff51173db0) = -1 ENOENT (No such file or
directory)
lstat("/home/cullmann/tmp/.git/HEAD", 0x7fff51173c70) = -1 ENOENT (No such file
or directory)
lstat("/home/cullmann/tmp/HEAD", 0x7fff51173c70) = -1 ENOENT (No such file or
directory)
stat("/home/cullmann", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
stat("/home/cullmann/.git", 0x7fff51173db0) = -1 ENOENT (No such file or
directory)
lstat("/home/cullmann/.git/HEAD", 0x7fff51173c70) = -1 ENOENT (No such file or
directory)
lstat("/home/cullmann/HEAD", 0x7fff51173c70) = -1 ENOENT (No such file or
directory)
stat("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat("/home/.git", 0x7fff51173db0)  = -1 ENOENT (No such file or directory)
lstat("/home/.git/HEAD", 0x7fff51173c70) = -1 ENOENT (No such file or
directory)
lstat("/home/HEAD", 0x7fff51173c70) = -1 ENOENT (No such file or directory)
stat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat("/.git", 0x7fff51173db0)   = -1 ENOENT (No such file or directory)
lstat("/.git/HEAD", 0x7fff51173c70) = -1 ENOENT (No such file or directory)
lstat("/HEAD", 0x7fff51173c70)  = -1 ENOENT (No such file or directory)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 424073] Slow start on automounted home

2020-07-10 Thread Klaus Vink Slott
https://bugs.kde.org/show_bug.cgi?id=424073

Klaus Vink Slott  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #4 from Klaus Vink Slott  ---
Thanks for taking time to answer this although it was not the answer I was
hoping for. To me it seems that kate is crippled in a professional environment
with automounted user catalogs.
I'll take a look if I can improve the situation by making the automounter
ignore . prefixed mountpoints.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 424073] Slow start on automounted home

2020-07-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=424073

--- Comment #3 from Christoph Cullmann  ---
Kate will search upwards up to the root. (or at least some levels, e.g. for
.kateconfig files, too)

There is no way to blacklist directories and I will not start to add such a
feature given there are multiple things that scan upwards.

That in your case this leads to unfortunate delays is not nice, but I see no
generic solution for that. (one could think to not span file system borders,
but that would be needed to implemented, too)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 424073] Slow start on automounted home

2020-07-10 Thread Klaus Vink Slott
https://bugs.kde.org/show_bug.cgi?id=424073

Klaus Vink Slott  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|INTENTIONAL |---
 Status|RESOLVED|REOPENED

--- Comment #2 from Klaus Vink Slott  ---
Please allow me a second round to get this confirmed:

Note that I am not talking about users home katalog, eg /home/user/.git These
is already mounted and accessible at launch and gives no delay.

But kate is searching for config files outside the current users home eg.
/home/.git - I have never seen any software having any configuration files at
this location.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 424073] Slow start on automounted home

2020-07-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=424073

Christoph Cullmann  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |INTENTIONAL
 CC||cullm...@kde.org

--- Comment #1 from Christoph Cullmann  ---
You can turn off the project plugin, that will avoid this. (this is intentional
to find the project valid for the currently launched Kate instance)

But even without that, e.g. other stuff that is typically in home will be
seearch, like the .config/* stuff.

-- 
You are receiving this mail because:
You are watching all bug changes.