On Sun, Jun 6, 2021 at 8:28 PM Oswald Buddenhagen <oswald.buddenha...@gmx.de> wrote: > > On Fri, Jun 04, 2021 at 05:45:19PM -0500, Felipe Contreras wrote: > >On Fri, Jun 4, 2021 at 3:17 PM Oswald Buddenhagen > ><oswald.buddenha...@gmx.de> wrote: > >> > >> On Fri, Jun 04, 2021 at 02:03:24PM -0500, Felipe Contreras wrote: > >> >I do want to place INBOX under Path, and since MapInbox is relative > >> >to > >> >Path, I take it to mean "./foobar", as opposed to "../foobar". > >> > > >> that is correct, but i don't see what argument you're trying to make > >> here. > > > >That by doing `MapInbox inbox` I'm telling mbsync that I want to do > >what the manual said I probably would want to do. > > > no, you're not. the use of "instead" would make no sense at all if it > referred to the same thing.
Not true. If a documentation says I can edit ~/.gitconfig, or $XDG_CONFIG_HOME/git/config instead, does that mean it cannot logically refer to the same thing? I can use "begin", or I can use "start" instead. Can they be the same thing? Ostensibly yes. > >> >> it *should* work if you remove the > >> >> Inbox def, but as the manual also says, SubFolders won't work for that > >> >> box then. > >> > > >> >This is not what the documentation says, it says: "this virtual > >> >mailbox does not support subfolders", that means subfolders do work > >> >just not under MapInbox. > >> > > >> where exactly do you see a semantic difference between the two? > > > >One affects the store, the other the mailbox. Store != mailbox. > > > there is no contratiction here, as the box is obviously a strict subset > of the store, and my message did not say or imply that the problem > extends beyond the box. I explicitly said I used "MapInbox inbox". Does that require subfolders? If not, and if the text says "This virtual mailbox does not support subfolders", and that only applies to this particular mailbox... How is that relevant to my case? > >> >This doesn't work: > >> > > >All right. Here is my config. And I'll send you the log. > > > >MaildirStore local > >Path ~/mail/ > >MapInbox foobar > > > >Channel gmail > >Pattern INBOX git > > > ok, the log shows that the option has no real effect whatsoever. so i > had a look at the code ... > firstly, it is rather primitive. it unconditionally adds the virtual box > to the listing. the implication of that is that the real inbox cannot > live under Path/NAMESPACE, as otherwise you get a duplicate. this is > unproblematic if the Patterns cover only one of the instances (as in > your case), but would otherwise cause quite a mess. > secondly, you misunderstood the mapping direction. it aliases the *real* > INBOX to the chosen name, which is also the one you'd need to use in the > channel's Patterns. > these imply that in practice, one would use the option only with an IMAP > store with an "inhomogeneous" box layout with INBOX outside Path, which > one wants to map into a homogeneous Path on the client. which is what i > wrote it for. I cannot parse that because you are a mixing stores. MapInbox is an option for *all** stores. Can you show me an example of a Maildir store that uses MapInbox correctly? -- Felipe Contreras _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
