From: Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: info-gnus-english@gnu.org
Subject: Re: imap acl editing broken
Date: Fri, 02 Aug 2013 11:27:34 +0200 [thread overview]
Message-ID: <87txj8788p.fsf@kosh.bigo.ensc.de> (raw)
In-Reply-To: <m3vc3ph8b9.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 01 Aug 2013 15:03:38 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> when using gnus v5.13 (bundled with emacs-24.1), the acl editing
>> (which worked fine in some previous versions), fails with
>>
>> | M-x gnus-group-nnimap-edit-acl
>> | gnus-group-nnimap-edit-acl: Autoloading failed to define function
>> | nnimap-acl-get
>>
>> Is there a chance that acl editing is supported again?
>
> I have no idea what acl editing is,
IMAP ACLs are described in http://tools.ietf.org/html/rfc4314 and their
modification worked already with previous gnus versions. Unfortunately,
the gnus version is both v5.13 in working and non-working case, but the
MUA (gnus v5.13 bundled with emacs-23.1 from RHEL 6.4) I am writing the
current message with, supports modification of ACLs. but other MUAs
(gnus v5.13 bundled with emacs-24.3 from Fedora 19) fail with message
above.
Working:
M-x gnus-group-nnimap-edit-acl
--> new buffer with
| ;;; Editing the access control list for `nnimap+...'.
| ;;;
| ;;; An access control list is a list of (identifier . rights)
| ;;; elements.
| ;;;
| ;;; The identifier string specifies the corresponding user. The
Non-working:
M-x gnus-group-nnimap-edit-acl
gnus-group-nnimap-edit-acl: Autoloading failed to define function nnimap-acl-get
Enrico
next prev parent reply other threads:[~2013-08-02 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16867.1357582045.855.info-gnus-english@gnu.org>
2013-08-01 13:03 ` Lars Magne Ingebrigtsen
2013-08-02 9:27 ` Enrico Scholz [this message]
2013-08-02 13:00 ` Lars Magne Ingebrigtsen
2013-08-02 14:17 ` Enrico Scholz
2013-08-03 11:40 ` Lars Magne Ingebrigtsen
2013-01-07 17:49 Enrico Scholz
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=87txj8788p.fsf@kosh.bigo.ensc.de \
--to=enrico.scholz@informatik.tu-chemnitz.de \
--cc=info-gnus-english@gnu.org \
--cc=larsi@gnus.org \
/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).