#473 mh-refile-msg vs mh-thread-refile

[Henrique Martins]

Seems that
  mh-refile-msg
sets the variables
  mh-last-destination
and
  mh-last-destination-folder
to be used in future refiles, but
  mh-thread-refile
does not sets those thus things can get a bit confusing if one does a few of each in succession.

Shouldn't the behavior be identical?

[Henrique Martins]

Looks like copying a few lines from mh-refile-msg to mh-thread-refile, and adding an optional argument to mh-thread-refile, like the one in mh-refile-msg does the trick.

Attaching patch.

[Mike Kupfer]

While we're at it, it seems like copying a message should remember/use the last target folder.

[Bill Wohler]

Good point, Mark. Thanks!

I use !' when a message doesn't have a default folder. If the last folder was changed with a copy (which I use mainly now to put in my +todo hierarchy), a subsequent!' would put the next message in +todo
(which I don't want) instead of the last folder I used for the
individual or company (which I do).

Mark Baushke mbaushke@gmail.com wrote:

I actually do not agree with such a change.

I often copy a message into a folder based on a topic and refile the same message into a
folder based on the mh-default-folder-list association. So, using ‘!’ to refile to the same
folder as the last target is good, but would be useless if it just refiled the message to the
same place I had just copied the message.

-- Mark

[Sent from my iPad -- Please pardon any auto-fix created typos.]

On Nov 20, 2020, at 9:13 PM, Mike Kupfer via mh-e-devel <mh-e-devel@lists.sourceforge.net>
wrote:

While we're at it, it seems like copying a message should remember/use the last target
folder.

------------------------------------------------------------------------------------------

[bugs:#473] mh-refile-msg vs mh-thread-refile

Status: open
Milestone: Unassigned
Labels: patch
Created: Fri May 10, 2013 12:41 PM UTC by Henrique Martins
Last Updated: Mon Apr 28, 2014 12:23 AM UTC
Owner: nobody

Seems that
  mh-refile-msg
sets the variables
  mh-last-destination
and
  mh-last-destination-folder
to be used in future refiles, but
  mh-thread-refile
does not sets those thus things can get a bit confusing if one does a few of each in
succession.

Shouldn't the behavior be identical?

------------------------------------------------------------------------------------------

Sent from sourceforge.net because mh-e-devel@lists.sourceforge.net is subscribed to 
https://sourceforge.net/p/mh-e/bugs/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/mh-e/admin/bugs/options. Or, if this is a mailing list, you can
unsubscribe from the mailing list.

_______________________________________________
mh-e-devel mailing list
mh-e-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mh-e-devel

---

Alternatives:

---

---

mh-e-devel mailing list
mh-e-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mh-e-devel

--
Bill Wohler wohler@newt.com aka Bill.Wohler@nasa.gov
http://www.newt.com/wohler/, GnuPG ID:610BD9AD

[Mike Kupfer]

The fix will appear in Emacs 31; commits b07a3970ae, 80c0529e94, and bc0eacca97.