Re: Enabling capability to have non-ascii folder names

2022-08-10 Thread Bence Ferdinandy
Sorry I thought you referred to some page with steps for debugging. After messing around for quite some time I realized that if I installed from master maybe I should not be looking at manpages online but check my local manpage, where I realized that the state folder has changed. Deleting that and

Re: Enabling capability to have non-ascii folder names

2022-08-10 Thread Oswald Buddenhagen
On Wed, Aug 10, 2022 at 12:12:33PM +0200, Bence Ferdinandy wrote: I've been trying to hunt down the debug instructions, but I haven't managed to find them :( from my first response to you: what's the output of `mbsync -l -a -Dn`? (actually, use -D, not -Dn) __

Re: Enabling capability to have non-ascii folder names

2022-08-10 Thread Bence Ferdinandy
I've been trying to hunt down the debug instructions, but I haven't managed to find them :( In the meantime I did find in the man pages that there's a folder called .mbsync, after deleting that at least I managed to confirm that with the master branch the names are indeed not garbled and for a sho

Re: Enabling capability to have non-ascii folder names

2022-08-09 Thread Oswald Buddenhagen
On Tue, Aug 09, 2022 at 11:38:42PM +0200, Bence Ferdinandy wrote: Is there anything else I need to delete to get a clean slate? Other than MaildirStore Paths? that depends on your config file. the debug instructions i posted are still valid, too.

Re: Enabling capability to have non-ascii folder names

2022-08-09 Thread Bence Ferdinandy
I built the newest version from master configuration output: Using SSL Using SASL Using zlib Not using Berkeley DB I deleted the folders and ran mbsync again, but now my previous config doesn't work, instead I get a "cannot be opened" error, with still garbled names: Opening far side box T&APY-r

Re: Enabling capability to have non-ascii folder names

2022-08-09 Thread Oswald Buddenhagen
On Tue, Aug 09, 2022 at 09:38:47PM +0200, Bence Ferdinandy wrote: Should switching to master solve this? yes ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Enabling capability to have non-ascii folder names

2022-08-09 Thread Bence Ferdinandy
I'm using 1.4.4 from the Ubuntu repo (isync/jammy,now 1.4.4-3 amd64 [installed]), which seems to be the latest release as far as I can tell. The command output is a long list of folders across all my accounts with the non-ascii stuff garbled like in the previous example. Should switching to master

Re: Enabling capability to have non-ascii folder names

2022-08-09 Thread Oswald Buddenhagen
On Tue, Aug 09, 2022 at 08:49:28PM +0200, Bence Ferdinandy wrote: I also have folder with names like 'cikkhozz&AOE-f&AOk-r&AOk-s' both from gmail and microsoft imap accounts, so if there's a fix for this I'd be very much interested. are you using an mbsync build from git master? if so, what's

Re: Enabling capability to have non-ascii folder names

2022-08-09 Thread Bence Ferdinandy
I also have folder with names like 'cikkhozz&AOE-f&AOk-r&AOk-s' both from gmail and microsoft imap accounts, so if there's a fix for this I'd be very much interested. Thanks, Bence Oswald Buddenhagen ezt írta (időpont: 2022. aug. 9., K, 15:15): > On Tue, Aug 09, 2022 at 11:10:20AM +0200, Sonia

Re: Enabling capability to have non-ascii folder names

2022-08-09 Thread Oswald Buddenhagen
On Tue, Aug 09, 2022 at 11:10:20AM +0200, Sonia Morales wrote: but is disabled by default. if the server doesn't support UTF-8, isync will just use UTF-7, so this isn't a relevant consideration. what is the actual problem you're seeing? ___ isync-