nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Remember "show" settings per project

mac mac1

Hi,

Currently, the "show" (Pending, Conflicts, ..., All) setting of the browser window seems to be sort-of global: when opening a project window it is opened with the last selected "show" setting.

Is it possible to remember this setting per-project?

Most of the time I have it set to "Pending", but for some projects I like it to be "All" (eg. my gitolite configuration repo)

Accepted answers

stevestreeting

Most of the detail filters are global on the assumption that you want to see things the same way most of the time and not have to switch for every repo you open. But I guess the file filter perhaps makes more sense as a per-repo setting, I've logged this: https://jira.atlassian.com/browse/SRCTREE-1329

All comments

stevestreeting

mac mac1

Thanks.

Looking into the matter some more, I've found that when I:

Open repo A (files pending showing)
Open repo B (also "peding")
Change files filter to "all" for B
Close B

I have the following situation: "files all" is stored as my preference, but repo A is still showing "peding".

When I now

Close repo A (showing pending)
Open repo A

The repo A will open with the files filter set to "All".

I'm afraid, to me, this is not a very consistend UI...

For me, I use "flat view" most of the time. The "show" option varies per project, but is mostly on pending. The context view settings mainly depend on the language I'm writing in or the project I'm working on, but most of the time it's 6 lines, diff parent, ignore \w.

My gut feeling is that the "view filters" (flat/tree/column; peding/conflict/.../all; #lines; diff parent/merged; ignore \w) should be project-saved, not global saved.

You would only have to set your preferred settings once (on project start). After that, it would be saved, right?

Then the settings for a new project could be a preference setting? (this is getting out of control !!! ;-)

I'm courious how other people have their settings and handle changes per project (if they do)...

stevestreeting

Yeah, this is because the default setting is altered when you change it, not based on the last window to close. So the last option you explicitly picked is the default next time. This will not be an issue if the setting is saved per repo.