From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Tarvi Verro <tarvi.verro@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] vim: Patch Ruby Mail's depracated method
Date: Tue, 25 Jun 2019 16:36:55 -0400 [thread overview]
Message-ID: <877e99v1ug.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20190318141051.9355-1-tarvi.verro@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Mon 2019-03-18 15:10:51 +0100, Tarvi Verro wrote:
> Method is not supported in Ruby's Mail 2.8.0+.
> ---
> vim/notmuch.vim | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/vim/notmuch.vim b/vim/notmuch.vim
> index ad8b7c80..541698cd 100644
> --- a/vim/notmuch.vim
> +++ b/vim/notmuch.vim
> @@ -666,7 +666,7 @@ ruby << EOF
> date = Time.at(e.newest_date).strftime(date_fmt)
> subject = e.messages.first['subject']
> if $mail_installed
> - subject = Mail::Field.new("Subject: " + subject).to_s
> + subject = Mail::Field.parse("Subject: " + subject).to_s
> else
> subject = subject.force_encoding('utf-8')
> end
> --
I see this patch is marked "notmuch::moreinfo", but i don't see any
request for more info specifically, so i thought i'd fill that in here.
I don't know vim or ruby, but i would expect a patch like this to
contain at least a pointer to Ruby's Mail package's documentation about
a backward-incompatible change introduced in a certain version, if not
documentation about the expected upgrade path. Can you provide those
pointers?
Thanks for offering fixes to the notmuch-vim codebase!
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-06-25 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 14:10 [PATCH] vim: Patch Ruby Mail's depracated method Tarvi Verro
2019-06-25 20:36 ` Daniel Kahn Gillmor [this message]
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=877e99v1ug.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.org \
--cc=tarvi.verro@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.
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).