Yeah, I think metaedit was created as an ad-hoc solution to edit commit
messages, and then grew some flags for user and date, and even --fold
for some reason. Internally it can prevent editor from opening (e.g.
when -m or -l is present), but there's no way to do it from CLI. It's
not a very
Faheem Mitha escribió/skribis/wrote/scrit (2023-04-07T23:39:45+0530):
> If you just want to change the user or date of the commit, there are
> separate flags for that. Namely, -u, -U, -d, and -D.
>
> Have you not looked at the help? See below.
Yes, I had read the help and tried all options.
>
Hi Marco,
See below.
On Fri, 7 Apr 2023, Marcos Cruz wrote:
Faheem Mitha escribió/skribis/wrote/scrit (2023-04-07T22:18:48+0530):
Yes, normally metaedit is intended to edit the existing commit message.
Hence it's natural to open an editor. What's the problem with that?
I'm converting my
Faheem Mitha escribió/skribis/wrote/scrit (2023-04-07T22:18:48+0530):
> Yes, normally metaedit is intended to edit the existing commit message.
> Hence it's natural to open an editor. What's the problem with that?
I'm converting my last Fossil repos to Mercurial.
The other day I had to fix the
Hi Marcos,
On Fri, 7 Apr 2023, Marcos Cruz wrote:
Evolve's `metaedit --user` and `metaedit --date` always open the commit
message in order to edit it. There's no way to prevent it?
Yes, normally metaedit is intended to edit the existing commit message.
Hence it's natural to open an
Evolve's `metaedit --user` and `metaedit --date` always open the commit
message in order to edit it. There's no way to prevent it?
--
Marcos Cruz
http://programandala.net
___
Evolve-testers mailing list
evolve-test...@lists.mercurial-scm.org
