From: Michal Sojka <sojkam1@fel.cvut.cz>
To: fauno <fauno@kiwwwi.com.ar>, notmuch@notmuchmail.org
Subject: Re: file-error "not a regular file"
Date: Wed, 30 Dec 2015 10:38:22 +0100 [thread overview]
Message-ID: <8737ukcm41.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <878u4e9jkx.fsf@endefensadelsl.org>
Hi fauno,
On Tue, Dec 29 2015, fauno wrote:
> David Bremner <david@tethera.net> writes:
>
>> I guess the tl;dr is that I can't duplicate this problem. Looking at the
>> traceback Peter provided, it looks like he is using
>> "send-message-without-bullets" to send the message. Since this isn't a
>> notmuch function, it's likely bypassing the notmuch fcc setup that
>> notmuch-mua-send and notmuch-mua-send-and-exit do.
>
> i've found the issue. i'm using jl-encrypt that expects email written
> in message-mode, and since notmuch is now a minor mode some functions
> that were expected to be there didn't work anymore.
can you share more details about how do you use jl-encrypt and which
functions do not work? Recently, I posted a few patches that fix some
problems related to the replacing message-mode with
notmuch-message-mode. Maybe, there is more what we can do to not break
user's setups.
From a brief look at jl-encrypt, it seems it is tightly bound to gnus,
because it uses gnus-message-setup-hook. Maybe it will work again with
notmuch if you use my patch [1] and run
(add-hook 'message-setup-hook 'jl-encrypt-if-possible)
-Michal
[1] id:1450690875-2111-2-git-send-email-sojkam1@fel.cvut.cz
next prev parent reply other threads:[~2015-12-30 9:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 3:07 file-error "not a regular file" Peter Salazar
2015-12-28 4:01 ` fauno
2015-12-28 14:46 ` David Bremner
2015-12-29 0:36 ` fauno
2015-12-30 9:38 ` Michal Sojka [this message]
2015-12-30 14:14 ` notmuch-mua and jl-encrypt (was: file-error "not a regular file") fauno
2016-01-02 21:24 ` Michal Sojka
2015-12-29 5:54 ` file-error "not a regular file" Peter Salazar
2015-12-29 20:44 ` David Bremner
2015-12-29 21:34 ` Peter Salazar
2015-12-29 21:48 ` David Edmondson
2016-01-04 10:11 ` Peter Salazar
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737ukcm41.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=fauno@kiwwwi.com.ar \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).