Opened 16 years ago
Last modified 3 years ago
#6002 new enhancement
[PATCH] Adds an options to customize the default history mode
|Reported by:||Owned by:|
|Component:||version control/log view||Version:||devel|
|Severity:||normal||Keywords:||bitesized patch preferences|
I often uses "Follow copies" mode in revision log view. But trac requires 2 clicks to change mode.
I always want to use my trac in follow_copy mode.
The attached patch (against r6000) adds "default_copy_mode" and "default_verbose" options to trac.ini.
Change History (17)
by , 16 years ago
comment:1 by , 16 years ago
by , 16 years ago
session option patch against r6009
comment:2 by , 16 years ago
That makes sense. How about session_option.diff patch?
comment:3 by , 15 years ago
comment:4 by , 14 years ago
When using the darcs backend instead of svn, there is no real file "copy". The "follow copies" option determines whether trac will follow file *moves*, and the default value of stopping the history when a file has moved is almost never what any darcs user wants.
So it would be good to make this configurable (as in the original patch from miyamuko) or else perhaps have some way for the Trac-Darcs plugin to set it.
comment:5 by , 13 years ago
|Milestone:||next-major-0.1X → 0.13|
#3492 was closed as duplicate.
Patch looks good. This
get_session_option help could perhaps also be reused in other places (timeline? diff options?).
comment:6 by , 13 years ago
See also ticket:3360#comment:4 for a more general proposal to handle user preferences.
comment:7 by , 13 years ago
comment:8 by , 13 years ago
comment:9 by , 11 years ago
|Milestone:||1.0 → 1.0-triage|
Preparing for 1.0.
comment:10 by , 11 years ago
We could do that in the same way we store the ticket comment history mode.
(leaving on stable, as it might still be done in time for 1.0)
comment:11 by , 9 years ago
|Keywords:||preferences added; userpreferences removed|
comment:12 by , 8 years ago
comment:13 by , 7 years ago
comment:14 by , 7 years ago
|Milestone:||next-stable-1.0.x → next-stable-1.2.x|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:15 by , 3 years ago
|Milestone:||next-stable-1.2.x → next-stable-1.4.x|
I would propose this be made sticky on the session (like timeline filters) rather than adding a new option.