https://bz.mercurial-scm.org/show_bug.cgi?id=5501

            Bug ID: 5501
           Summary: Pager enabled now when people thought it was disabled
           Product: Mercurial
           Version: default branch
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: Mercurial
          Assignee: bugzi...@mercurial-scm.org
          Reporter: h...@pewpew.net
                CC: mercurial-devel@mercurial-scm.org

Important information that's relevant:

- this is happening at a company that pushes a centralized configuration
- that centralized configuration has historically enabled pager by these
configs:
- - extensions.pager=
- - pager.pager = less -FRX
- - pager.attend = <long list of aliases/commands>


We're rolling 4.1.1+290-7433b3bc55ee to our users (I can try to identify what
we previously had if it's relevant, but this is the first time we're picking up
the pager changes), and have two reports of users complaining because they
thought they'd disabled pager but now it's enabled again.

One user disabled it via 'extensions.pager=!'  (exclamation mark on the end ->
don't load extension)

One user disabled it via 'pager.attend = NONE'.


Both of the users that have raised the issue internally are now happy with
'pager.enable = False', but I wanted to file a bug since this is a set of
potentially unexpected changes, and to see if we wanted to do anything about
it.  Note: it doesn't require a company-wide centralized configuration, it
might be, for example, part of the OS distribution: if any common distribution
turns pager on for people and thus these kinds of "turn pager off" methods have
been put into people's hgrc files, we're now not respecting them.

Resolving as WONTFIX [behavior change is expected/intended/acceptable] is
probably OK, but I'd like someone who knows more about *exactly* what the BC
guarantees are to investigate before this gets closed :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Reply via email to