just guessing that it's the same menu item so it's the same action both
bound to MarkAsUnread: which almost certainly calls toggleReadState:
internally. If you select a mixed range of read and unread messages the
menu item defaults to "mark as read"
The difference being one is bound to a menu
On 1 Dec 2021, at 9:55, John Cooper wrote:
> On 1 Dec 2021, at 8:44, Randall Meadows wrote:
>> On 1 Dec 2021, at 6:48, John Cooper wrote:
>>> For what it’s worth, the following variation continues to work for me in
>>> 5850:
>>>
>>> "u" = ( "toggleReadState:" );
>>
>> I considered that, but logic
On 1 Dec 2021, at 11:44, Randall Meadows wrote:
> On 1 Dec 2021, at 6:48, John Cooper wrote:
>> For what it’s worth, the following variation continues to work for me in
>> 5850:
>>
>> "u" = ( "toggleReadState:" );
>
> I considered that, but logic tells me that it will be fruitless if my message
On 1 Dec 2021, at 8:44, Randall Meadows wrote:
> On 1 Dec 2021, at 6:48, John Cooper wrote:
>>
>> For what it’s worth, the following variation continues to work for me in
>> 5850:
>>
>> "u" = ( "toggleReadState:" );
>
> I considered that, but logic tells me that it will be fruitless if my
On 1 Dec 2021, at 6:48, John Cooper wrote:
> On 30 Nov 2021, at 17:13, Randall Meadows wrote:
>
>> and it works just fine. I'm trying to create an analog to mark selected
>> messages as READ, without luck; it just beeps at me after the second `r`.
>> I've tried several things along the
