Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@equator.com>
Subject: Re: nnimap subfolder problem
Date: 07 Dec 2001 09:23:20 -0800	[thread overview]
Message-ID: <r2g06n9c6v.fsf@kakarot.equator.com> (raw)
In-Reply-To: <iluk7vzp0mp.fsf@dhcp128.extundo.com>

Simon Josefsson <jas@extundo.com> writes:

> Kevin Hilman <khilman@equator.com> writes:
> 
> > If I tell Gnus to create folders with the '\' character it works fine,
> > however as new folders are created, I don't see them when i do a 'B'
> > (gnus-group-browse-foreign-server).  I can see them in the folder
> > listing of other clients (like Mozilla) though.  If I do a 'j'
> > (gnus-group-jump-to-group) and type the full group name (for example
> > nnimap+mailserver:foo\bar) I can get to it just fine.
> >
> > So, I have a couple of questions
> >
> > 1) How can the browse-foreign server pick up these folders and
> >    subfolders?
>
> It should find them automatically.  Do you see them if you do ^ and
> then RET on the IMAP server?  

No. If I use '.' or '/' as a separator, it will see those, but not when
using '\' .

> But there may be some quoting problem since elisp uses \ as a
> quoting character, and `read' is still used in some parts of
> imap.el.  Do you get anything weird in *Messages*?

Nothing suspicious in *Messages*

> > 2) Is there a way Gnus can be smarter about creating subfolders based
> >    on some existing hierarchy information?
> 
> What do you mean?  Gnus doesn't care about the hierarchy delimiter
> (and hence the hierarchy), you could use the Topic mode in the Group
> buffer to do some hierarchies though.

For example, in my nnimap-split-rule I use

  ("lists\\ding" "^Sender: owner-ding")

To put ding list messages into ding (a subfolder of 'lists') with '\'
as a separator (note it has to be escaped).

What I'd like is to have Gnus query the separator character from the
server and put it in a variable so I could then use

  ("lists" + gnus-imap-hierarchy-separator + "ding" ....)

To create folders on the server.  (I don't know lisp, so the syntax is
wrong) So it is portable across mail servers.  It took me a while to
figure out that Lotus Domino uses '\' as a separator character.

-- 
Kevin Hilman               ---  Equator Technologies, Inc.
khilman@equator.com        ---  Seattle, WA USA



  reply	other threads:[~2001-12-07 17:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 23:48 Kevin Hilman
2001-12-07 14:26 ` Simon Josefsson
2001-12-07 17:23   ` Kevin Hilman [this message]
2001-12-07 19:29     ` Simon Josefsson
2001-12-10 19:48       ` Kevin Hilman
  -- strict thread matches above, loose matches on Subject: below --
2001-10-16 11:13 Nicolas KOWALSKI
2001-10-16 11:41 ` Simon Josefsson
2001-10-16 12:02   ` Nicolas KOWALSKI
2001-10-16 12:35     ` Simon Josefsson
2001-10-16 13:04       ` Nicolas KOWALSKI
2001-10-16 13:32         ` Simon Josefsson
2001-10-16 13:46           ` Kai Großjohann
2001-10-16 14:01             ` Nicolas KOWALSKI
2001-10-16 18:12             ` Simon Josefsson
2001-10-17  4:27               ` Amos Gouaux
2001-10-16 13:59           ` Nicolas KOWALSKI
2001-10-16 18:27 ` Steinar Bang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=r2g06n9c6v.fsf@kakarot.equator.com \
    --to=khilman@equator.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).