Edgewall Software
Modify

Opened 12 years ago

Last modified 3 years ago

#6002 new enhancement

[PATCH] Adds an options to customize the default history mode

Reported by: miyamuko@… Owned by:
Priority: normal Milestone: next-stable-1.2.x
Component: version control/log view Version: devel
Severity: normal Keywords: bitesized patch preferences
Cc: martin@… Branch:
Release Notes:
API Changes:

Description

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.

Attachments (2)

log.diff (1.7 KB ) - added by miyamuko@… 12 years ago.
session_option.diff (1.5 KB ) - added by miyamuko@… 12 years ago.
session option patch against r6009

Download all attachments as: .zip

Change History (16)

by miyamuko@…, 12 years ago

Attachment: log.diff added

comment:1 by Noah Kantrowitz, 12 years ago

I would propose this be made sticky on the session (like timeline filters) rather than adding a new option.

by miyamuko@…, 12 years ago

Attachment: session_option.diff added

session option patch against r6009

comment:2 by miyamuko@…, 12 years ago

That makes sense. How about session_option.diff patch?

comment:3 by Christian Boos, 12 years ago

Milestone: 0.12

Interesting.

comment:4 by zooko@…, 11 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 Christian Boos, 9 years ago

Milestone: next-major-0.1X0.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 Christian Boos, 9 years ago

See also ticket:3360#comment:4 for a more general proposal to handle user preferences.

comment:7 by Christian Boos, 9 years ago

Keywords: userpreferences added

comment:8 by Martin Scharrer <martin@…>, 9 years ago

Cc: martin@… added

comment:9 by Remy Blank, 7 years ago

Milestone: 1.01.0-triage

Preparing for 1.0.

comment:10 by Christian Boos, 7 years ago

Keywords: bitesized added

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 Ryan J Ollos, 5 years ago

Keywords: preferences added; userpreferences removed

comment:12 by Ryan J Ollos, 5 years ago

Owner: Christian Boos removed

comment:13 by figaro, 4 years ago

Keywords: patch added

comment:14 by Ryan J Ollos, 3 years ago

Milestone: next-stable-1.0.xnext-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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.