From: Robert Pluim <rpluim@gmail.com>
To: soyeomul@doraji.xyz (Byung-Hee HWANG "(황병희, 黃炳熙)")
Cc: The Gnus <ding@gnus.org>, Vivishek Sudhir <vivishek.sudhir@gmail.com>
Subject: Re: gnus nnimap intermittent login failure
Date: Tue, 28 Nov 2017 14:51:31 +0100 [thread overview]
Message-ID: <874lpefr4s.fsf@gmail.com> (raw)
In-Reply-To: <yw147-han4350-65515e035f9e-1511873359-fsf@lambda.alex.chromebook> ("Byung-Hee HWANG \=\?utf-8\?B\?XCIo7Zmp67OR7Z2sLCDpu4PngrPnhpkpXCIiJ3M\=\?\= message of "Tue, 28 Nov 2017 21:56:47 +0900")
soyeomul@doraji.xyz (Byung-Hee HWANG "(황병희, 黃炳熙)") writes:
> In Article <m28teu3vxp.fsf@gmail.com>,
> Vivishek Sudhir <vivishek.sudhir@gmail.com> writes:
>
>> [...sorry for snip...]
>> (setq auth-sources '((:source "./authinfo.gpg"))) ; this is where to find the login details
>
> It's odd, "./authinfo.gpg" <-- What is it?
True. My auth-sources entries are all fully qualified
filenames. Looking through the auth-sources library, it uses
'file-exists-p', which will do filename expansion. Without a '~' in
the filename it will default to looking in the current directory. The
documentation also says:
If you have problems with the search, set ‘auth-source-debug’ to
‘'trivia’ and see what host, port, and user the library is
checking in the ‘*Messages*’ buffer. Ditto for any other
problems, your first step is always to see what’s being checked.
The second step, of course, is to write a blog entry about it and
wait for the answer in the comments.
Regards
Robert
next prev parent reply other threads:[~2017-11-28 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 21:11 Vivishek Sudhir
2017-11-28 12:56 ` Byung-Hee HWANG (황병희, 黃炳熙)
2017-11-28 13:51 ` Robert Pluim [this message]
2017-11-29 21:38 ` Vivishek Sudhir
2017-11-28 15:03 ` Adam Sjøgren
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=874lpefr4s.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ding@gnus.org \
--cc=soyeomul@doraji.xyz \
--cc=vivishek.sudhir@gmail.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).