[Bug 3972] New: qnew/qrecord editor does behave different from commit/record editor

mercurial-bugs at selenic.com mercurial-bugs at selenic.com
Fri Jun 28 06:12:47 CDT 2013


http://bz.selenic.com/show_bug.cgi?id=3972

          Priority: normal
            Bug ID: 3972
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: qnew/qrecord editor does behave different from
                    commit/record editor
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: zapster at zapster.cc
          Hardware: PC
            Status: UNCONFIRMED
           Version: unspecified
         Component: mq
           Product: Mercurial

There are several differences between the editor handling of the "normal"
repository commands (commit/record/...) and their MQ equivalents
(qnew/qrecord/...).

* mq does not strip "HG:" lines.
* mq does not respect $HGEDITOR
* mq does not generate "HG: changed ...", etc. comments
* mq does not abort if no commit message is entered (ok, this might be intended
this way but in my eyes -e implies that one wants to enter a message.)

>From what I can tell from skimming through the code the commands use quite
different methods. E.g. commit uses `cmdutil.commiteditor` while qnew invokes
`ui.edit`.

IMHO the behavior should be synchronized.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list