File Type Session Defaults

[Michael Bulgrien]

I believe this has come up before...

In my opinion, Importance, Alignment, and Replacements should not only only be defined as "default session settings", but there should also be the ability to create sets of session settings to override session defaults for a given file format. If no format-specific overrides are defined use the session defaults. In other words, instead of two items in the Session Settngs drop down:

Use for this view only
Also update session defaults

There should be three:

Use for this view only
Use as file format default
Update session defaults

Under the File Formats dialog, there should be a button to clear the format-specific overrides and just use the session defaults instead.

[Michael Bulgrien]

The prior discussion on this topic began here and was continued here in October 2007.

[Thyresias]

I came here to complain on the very same subject: I need "Importance" and "Alignment" defaults to be set on a per file-type basis, as in BC2.

The prior discussion on this topic began here and was continued here in October 2007.

I read (part of) the posts you are referring to. I understand the point of the dev team, giving code review as an example. But here is something I want to do, and I can't:
- in *.txt files, for me, character case differences are unimportant by default
- in *.rb or *.java files, they are important

I'm trying to think about how the different point of views could be matched. Let's see:

1. The dev team wants per-session settings where they can say "comments differences are unimportant, whatever the file type".

2. We want per-file default settings.

Couldn't it work that way:

1 - default settings at a root level, for all file types, as BC3;
2 - specific settings on a per-file basis (equal to the root if not set), like in BC2;
3 - possibility to override for all file types on a per-session basis, as BC3.

Unless I do not use the new version well?

To sum up: great release, thanks a lot, but for me, this point is so far the only one where there is a regression in functionality, which surprises me given the overall extremely high quality of your software (chapeaux bas, as we say here = hats down ). Do you plan to do something about it?

Thierry

[Tim]

In BC3, you can define grammar elements (by file type) as case-sensitive. Notice that keywords in Java are case-sensitive, but for example Delphi keywords are not.

Out of the box, .txt files are not associated with a grammar, so all the text is "default text" - with importance of case controlled by the session settings.

Is this not working correctly for you?

[Tim]

Couldn't it work that way:

1 - default settings at a root level, for all file types, as BC3;
2 - specific settings on a per-file basis (equal to the root if not set), like in BC2;
3 - possibility to override for all file types on a per-session basis, as BC3.
Thierry

This is one of the designs we are considering for a future version.

Thanks,

[Thyresias]

Tanks for your answers, Tim.

Out of the box, .txt files are not associated with a grammar, so all the text is "default text" - with importance of case controlled by the session settings.
Is this not working correctly for you?

I sure will survive that way
But the real point is I'm almost never using sessions, because there would be tens if not hundreds of them (I use your product all the time, everywhere on my disks and between my machines): I just use the explorer right-click stuff, so per-file defaults work better for me.

This is one of the designs we are considering for a future version.

Great news.

Thanks again for your wonderful software. And full edit in file comparison is sooo handy!