[neomutt-users] Save email in new folder does not work

[Pietro Cerutti]

> On 3 Jul 2019, at 20:55, tuxic at posteo.de wrote:
> 
> On 07/03 10:44, Pietro Cerutti wrote:
>> On Jul 03 2019, 02:26 UTC, tuxic at posteo.de wrote:
>>> On 07/01 08:59, Pietro Cerutti wrote:
>>>> On Jun 30 2019, 18:43 UTC, Pietro Cerutti <gahr at gahr.ch> wrote:
>>>>> 
>>>>> 
>>>>>> On 30 Jun 2019, at 05:48, tuxic at posteo.de wrote:
>>>>>> 
>>>>>> When saveing an email from one folder to one, which does not exist,
>>>>>> neomutt asks me whether to create that (new) folder. When answering
>>>>>> [yes], the message "Copying to /home/user/myfolder..." appears and
>>>>>> remains there.
>>>>>> 
>>>>>> Neither the message gets copied nor the new folder is created.
>>>>> 
>>>>> Yep, I can reproduce it by a simple “save” to a non-existent path. I
>>>>> have the impression we’ve fixed this bug before and it’s crept in again.
>>>>> 
>>>>> I’ll try to have a look tomorrow-ish.
>>>> 
>>>> Tracking this here:
>>>> https://github.com/neomutt/neomutt/issues/1762
>>>> 
>>>> --
>>>> Pietro Cerutti
>>>> 
>>> 
>>> Hi Pietro,
>>> 
>>> I saw https://github.com/neomutt/neomutt/commit/12e79d658788f64f4a9e35ea435c7eb37ab23df8
>>> and Flatpack has fixed it.
>>> 
>>> I git pulled my repo and build a new neomutt...but the bug is still
>>> there.
>>> 
>>> Did I something wrong updateing my repo?
>> 
>> Uhm, that's surprising. The latest master works fine for me, wrt saving an
>> email to a non-existent local path.
>> 
>> What's the output of your `neomutt -v`?
>> 
>> -- 
>> Pietro Cerutti
>> 
> Hi Pietro,
> 
> I updated and rebuild the repo a few minutes ago again.
> 
> neomutt -v says:
> NeoMutt 20180716

You’re running last year’s version. It’s the last official release. My wild guess is that you’re running as “neomutt” as opposed to “./neomutt” from the checkout, and your shell is picking the installed versions from some package system.

— 
Pietro Cerutti