Re: How to move from end of one thread to beginning of next by pressing "n"?

On Mon, Apr 08 2024, Richard H. Stanton wrote: > If I press RETURN to view a message, “n” and “p” move to the > next/previous message *in the thread*, but motion with “n” stops when > you get to the end of the thread. Is there a way to set things so that > “n” moves from the end of the current

Re: notmuch.el, needs without-restriction to properly save draft

On Wed, Mar 13 2024, Marc Fargas wrote: > Hi there, Hi, Marc! > I'm not sure if this is the appropiate mailing list for bugs regarding > notmuch.el (Notmuch in Emacs). Also, I'm not subscribed so please keep > me in CC! Yes, this is a fine place to report things > I recently noticed that when

Re: Getting read out of inbox

On Mon, Nov 27 2023, Caleb Herbert wrote: > Hi, Hi Caleb, > I have a stupid newbie question. No problem at all. > I just started using Notmuch, opened my email in Emacs, and was > bombarded by a bunch of old mail. My email was perfectly sorted in > Icedove (Thunderbird) before I made the

Re: macOS and go language bindings

On Tue, Nov 21 2023, Peter Lawrence wrote: > Thanks for the feedback, Carl! No problem. I'm glad you were able to push even a little past what I was able to do. > I have a feeling now that this isn't just a macOS issue, but possibly a > broader issue that would effect anyone using a newer

Re: macOS and go language bindings

On Sun, Nov 19 2023, Peter Lawrence wrote: > Hi. Hi Peter! > I'm trying to build an email client (aerc) with support for notmuch > on macOS. aerc is written in go. I can't find an aerc package for brew > which includes notmuch headers/library files. Where can I get these > language bindings

Re: "notmuch compact" questions

Hi Andy, I'm really glad the compaction was so successful! I think the Xapian folks deserve the big credit for this, more than any code specific to notmuch, (other than user interface and safety checking/backup, etc.). I'm really glad you're finding notmuch helpful. And I'm glad you felt

Re: Selection bug

On Tue, Apr 04 2023, Justus Winter wrote: > My desktop now behaves exactly like my laptop, and it is really > annoying. Surely I'm not the only one with this problem. Can no one > else reproduce this? I haven't tried using the reproduction test, but I did just refresh my inbox and I saw the

Re: Data loss

On Tue, Apr 04 2023, Michael J. Gruber wrote: >> It's really unfortunate if notmuch-mutt makes it that easy to throw away >> your email. >> >> That sounds like a nasty bug that should be fixed in that program. > > To be fair to notmuch-mutt: > ``` > --output-dir DIR > > Store search results as

Re: Data loss

;> >> First of all: Do you have a back-up? > > G, no :-(( > >> >> notmuch itself does not delete mails, as Carl pointed out. In addition >> to notmuch you mentioned notmuch-mutt. Did you run that manually or >> using some mutt config? > > Yes

Re: Help in Emacs config

On Tue, Mar 07 2023, Atanas Janackovski wrote: > I have justed strated using `notmuch' in Emacs (doom configuration), > and I love it! Great! I'm glad it's useful for you. > 1. I have a number of accounts that I use. How do I configure my > config to save draft messages based on the "From"

Re: Thanks for notmuch-lore

On Tue, Mar 22 2022, Kyle Meyer wrote: > I may be missing something (I didn't know about notmuch-lore before > seeing it mentioned here), but it looks like the initialization step of > notmuch-lore's pre-new handles that already. You just need to set > `since` far enough back: Hmm... I did see

Thanks for notmuch-lore

On Tue, Feb 01 2022, Tobias Waldekranz wrote: > I actually gave up on getting my mailinglists from my email provider, > now I just download it directly from lore. I hacked together a script > that will scrape a public-inbox repo and convert it to a Maildir: > > https://github.com/wkz/notmuch-lore

Confusing message from notmuch-maildir-fcc-with-notmuch-insert

Hi folks, I just setup notmuch from scratch for the first time in a very long time, (as in, for the first time since I created notmuch originally). And first, thanks to everyone who has kept notmuch going along so well! It's delightful for me to see how much it keeps improving in the time I have

Re: [PATCH] emacs: add global tag history

On Wed, Jan 26 2022, inwit wrote: >> Even that will not be perfect (since the messages matching the query >> could change behind emacs back), but close enough for most interactive >> use, maybe? > > I was thinking about saving the IDs of the messages affected by the > change, but I still don't

Re: Dodo: a new graphical, hackable frontend for notmuch

On Tue, Jan 04 2022, Aleks Kissinger wrote: > We all like to unwind in different ways over the holidays. For me, I > decided to write a new GUI frontend for notmuch based on PyQt. > > It's called Dodo: https://github.com/akissinger/dodo Cool! I'll be excited to check this out. > p.s. I added a

Re: Statistics about senders with notmuch possible?

On Mon, Dec 27 2021, signmeup wrote: > I would like to create some kind of statistics to see from which sender > I've got the most emails, having something like a TOP 10 list. > [ 4 more citation lines. Click/Enter to show. ] > In the end of every year I delete all my emails, which are not marked

Re: Inconsistencies in handling command flags: `--flag=value` different than `--flag value`

On Wed, Apr 29 2020, Jameson Graef Rollins wrote: > I dare say there are few people that have muscle memory for the notmuch > command line (especially for notmuch show), and fewer that aren't > themselves developers... Here, the concern isn't just "muscle memory" (forcing users to learn how to

Re: Weird tagging issue

On Mon, Mar 30 2020, Brian May wrote: > This applies to all 4 of those messages. Yes, they all look like they > have the same Message-ID 4 different messages all with the same message ID definitely violates a core assumption of notmuch (that each message as a unique message ID). I think it would

Re: email recipient not taken into account when replying?

On Wed, Jan 08 2020, Alan Schmitt wrote: > Is there another way to tell notmuch to use as From address the address > the email was sent to, if it's one of my emails? Yes. The user.other_email configuration entry should do that. For example, in ~/.notmuch-config: [user] name=Alan Schmitt

Re: script to move messages according to tags

Yes, Notmuch considers any email files with the same message-id header as being the same message so won't show you multiple versions of the same email, (unless you're specifically asking for it to with something like --output=files). In normal usage I never worry about the duplicates I get from

Re: [PATCH] Display extra headers for emacs-mua - db config option

On Thu, Nov 21 2019, Johan Parin wrote: > Johan Parin writes: >> Daniel Kahn Gillmor writes: >>> >>> Is it that much worse to pass around the notmuch_database_t *? My opinion is that we should not use the static notmuch_database_t pointer. I think any desire to reach for that is, at best,

Re: Workaround for Exchange-corrupted PGP/Mime structure

On Wed, Nov 20 2019, Carl Worth wrote: > I'll update my notmuch and give this a try. Just a "git pull; make; make install" and my problem went away. Thanks again for the fixes, Daniel. -Carl signature.asc Description: PGP signature __

Re: Workaround for Exchange-corrupted PGP/Mime structure

On Wed, Nov 20 2019, David Bremner wrote: > There's some recent work by dkg in (currrently unreleased) commits on > master. "git log -Smangled" Thanks, David, and Daniel! Those commit messages look very useful to me. I'll update my notmuch and give this a try. -Carl signature.asc

Workaround for Exchange-corrupted PGP/Mime structure

I recently received a GPG-encrypted message that notmuch was not able to handle transparently as I'm used to. (That is, instead of decrypting the message and verifying the signature inside, etc.—instead I was just presented with an attachment that contained the encrypted message.) After some

Re: [FEATURE] indexing arbitrary headers

On Thu, May 30 2019, Daniel Kahn Gillmor wrote: > I just wanted to point out that this specific request has now been added > to notmuch, thanks to David Bremner! It will hopefully be part of the > forthcoming 0.29 release: Woo-hoo! Thanks so much!! This has been on my

Re: how to search for hyphenated words? (was: how to search for Morse code?)

On Tue, Mar 12 2019, Gregor Zattler wrote: > what I do not understand is that it dosn't matter if I search for > > org-notmuch > > or > > "org-notmuch" > > '"org-notmuch"' > > or even > > org ADJ/1 notmuch Correct. All four of those forms are giving you phrase searches, (so a term "org" followed

Re: how to search for hyphenated words? (was: how to search for Morse code?)

Hi Gregor, The trick here is that when notmuch is indexing body text it feeds it into a Xapian function that parses the text by finding "terms" in the text. And this parser considers both punctuation and whitespace as separators between terms. So your messages are not being indexed in a way to

Re: travis build env switched to xenial

On Wed, Mar 06 2019, David Bremner wrote: > Those of you about to tell me how much better FreedomAvocadoCI [2] is > than Travis are encouraged to set up instances and we can try it out. As > long as Carl doesn't object, I would be interested in a setup where we > run e.g. webhooks directly on

Re: Emacs and the missing 'g'

On Tue, Feb 12 2019, Matt Armstrong wrote: > I'm returning to notmuch after a hiatus. It is still nice! Glad to hear it! Welcome back. > Most notmuch modes are "special" modes -- i.e. their text is generated > by Emacs and does not reflect a file. In these modes 'g' has > traditionally been

Re: Release signatures

On Sun, Feb 10 2019, David Bremner wrote: > Adam Majer writes: >> The releases are signed in a funny way. The .asc file are not detached >> signatures of the checksum, but actually contain it inside the .asc file. >> >> # gpg -v --verify notmuch-0.28.1.tar.gz.sha256.asc >> ... >> gpg: binary

Re: question about deletion and counts

On Sat, Nov 03 2018, Jeff Templon wrote: > No new mail. Removed 577 messages. Detected 89 file renames. > > 577 + 89 = 666 ... my guess is that there were 577 messages and 89 files > that represented duplicates of messages. Yes. Among the messages you had tagged as deleted you had 577 unique

Re: finding file by size

On Tue, Nov 06 2018, Ralph Seichter wrote: > I'm not sure about using Notmuch itself, Right. Notmuch doesn't currently index (as far as I'm aware) anything that would be useful for sorting by size. > but this should work: > > find /path/to/maildir -type f -size +50M | xargs rm Hmm... I

Re: tell me how to do this (mass tagging of messages)

On Wed, Oct 17 2018, Jeff Templon wrote: > Indeed, as long as I am satisfied that all the messages in the view are > OK to delete / tag / whatever ... I usually look at such at view to make > sure that eg. the SPAM filter is doing the right thing. I have not found any case in the notmuch-emacs UI

Re: tell me how to do this right (mail sent to lists)

On Tue, Oct 09 2018, Jeff Templon wrote: > So here’s the deal : I am tagging with afew, it has a special mailing > list filter, which does the right thing - it tags the copy that was > delivered from the mailing list with the list name. I think you may be mistaken about the above details. If the

Re: notmuch shows tag which is not on any email

On Mon, Jun 04 2018, Gregor Zattler wrote: > Dear notmuch developers, Hi, Gregor! > does notmuch remember tags even if at time of query there is no > message tagged with the respective tag?: No. At least, from when I originally invented the notmuch schema, tags only existed on messages and

Re: a temporary nmweb view of notmuch mailing list archive

On Sun, Feb 04 2018, Daniel Kahn Gillmor wrote: > I did a bit of experimenting with Brian Sniffen's proposed notmuch-web > branch, and it's now (temporarily) publishing a view of the notmuch > mailing list here: > > https://nmbug.notmuchmail.org/btsmail/ Thanks, Brian and Daniel! When I

Re: Fetching from the git repositories over https?

On Sun, Jan 28 2018, Adam Plaice wrote: > I apologise if I'm asking in the wrong place. Not at all. This is the right place. > Is it possible to clone/fetch from the notmuch git repositories > (particularly https://git.notmuchmail.org/git/notmuch) over https > rather than with the `git://'

Re: [PATCH] debian: drop export-dir from gbp.conf

On Tue, Feb 06 2018, Daniel Kahn Gillmor wrote: > No one knows why this invocation is here. it does weird things during > the build. If a developer really wants this behavior, they can > specify it in their own ~/.gbp.conf I imagine I'm to blame for this one? One of the things that has always

Re: Possible bug with named queries

On Wed, Dec 13 2017, David Bremner wrote: > STORED IN DATABASE, thanks to some doc cleanup by dkg. In general I'd > recommend using using "notmuch config" for all configuration changes, > then you don't have to keep track of which ones are stored in > .notmuch-config. Really? We're deprecating

Re: notmuch.el: controlling what does and doesn't get expanded in searches

On Thu, Aug 04 2016, Matt Armstrong wrote: > Yes, I find the query semantics with respect to tags and threads a bit > confusing at times. This is not a problem specific to notmuch, as I > find the same kinds of issues in GMail. Usually the problem occurs at > the semantic border between

Re: Push to wiki fails with "cannot run hooks/pre-receive" error

On Wed, Mar 23 2016, J. Lewis Muir wrote: > I just tried to push a minor fix to the wiki, but I get the following > error: ... > remote: error: cannot run hooks/pre-receive: No such file or directory Oops. My mistake. I recently converted all user-space packages on the server from 32-bit to

Re: Notmuch -- Just an email system

On Sat, Mar 12 2016, David Bremner wrote: > I'm not carl, but you can find information about licensing of the wiki > material here > > https://notmuchmail.org/COPYING/ > > We'd be happy to host a russian version of some of the pages on the > wiki; see > >

Re: Stolen email list?

On Thu, Mar 03 2016, David Bremner wrote: > Johnny Utahh writes: > >> I recently received email sent to my notmuch-based email address that >> was clearly spam. I suspect that notmuch@notmuchmail.org email-address >> list may have been stolen. If you're not

Re: NOTMUCH_STATUS_LAST_STATUS problematic across additive library upgrades

On Mon, Dec 07 2015, Daniel Kahn Gillmor wrote: > I note that it's exposed in the go bindings -- maybe it shouldn't be > exposed in any of the bindings that can avoid exposing it? Quite likely. It's only there in C because there's no other way to know the bounds for iterating over all possible

Re: elisp + company completion patches, v7

On Sun, Oct 25 2015, Tomi Ollila wrote: > I, if this does not sound nitpicking, would amend those 'This patch' and > 'With this patch' texts in commit messages away by some rewording -- those > pose as a bad example for someone reading the code -- and diminish the > effect when I complain that

Re: [PATCH] doc: update copyright year

On Thu, Oct 15 2015, Tomi Ollila wrote: > -copyright = u'2014, Carl Worth and many others' > +copyright = u'2015, Carl Worth and many others' I think the correct approach to copyright here is to expand the range of years, (so "2014-2015") rather than increment it. Presu

Re: correct way to search for only PDF attachments

On Mon, Sep 28 2015, Xu Wang wrote: > I would look to look for all emails from a colleague jongho. I tried: > > from:jongho attachment:pdf > > which seems to do as I wanted. Good. That should work. > To understand more, what does the following search for? > > from:jongho attachment:.*pdf Uhm,

Website and mailing list are hopefully back now

On Fri, Apr 03 2015, Carl Worth wrote: > The notmuchmail.org server experienced a catastrophic failure a few days > ago. I gave up on getting access to that server anymore, and have > instead brought things back up on a separate server that I had > available, (and to which I have actu

Website and mailing list are hopefully back now

Hello all, The notmuchmail.org server experienced a catastrophic failure a few days ago. I gave up on getting access to that server anymore, and have instead brought things back up on a separate server that I had available, (and to which I have actual, physical access this time). I restored the

Website and mailing list are hopefully back now

Hello all, The notmuchmail.org server experienced a catastrophic failure a few days ago. I gave up on getting access to that server anymore, and have instead brought things back up on a separate server that I had available, (and to which I have actual, physical access this time). I restored the

Re: Website and mailing list are hopefully back now

On Fri, Apr 03 2015, Carl Worth wrote: The notmuchmail.org server experienced a catastrophic failure a few days ago. I gave up on getting access to that server anymore, and have instead brought things back up on a separate server that I had available, (and to which I have actual, physical

Re: [PATCH 07/11] lib: Implement ghost-based thread linking

On Fri, Oct 03 2014, Austin Clements wrote: This updates the thread linking code to use ghost messages instead of user metadata to link messages into threads. In contrast with the old approach, this is actually correct. Hi Austin, I've read through your commit messages, (not the code), and I

Re: [PATCH] cli: Be more helpful when .notmuch-config does not exist

Austin Clements amdra...@mit.edu writes: Since this condition is expected for new users, this patch adds specific handling for the file-not-found case to give a message that is friendly and actionable. ... + fprintf (stderr, Configuration file %s not found.\n +

Re: [PATCH v2] emacs: jump: sort-order bugfix

Mark Walters markwalters1...@gmail.com writes: The symptom is that if you are in a search buffer and use notmuch jump to run a saved search which does not have an explicitly set sort order then the sort order of the saved-search is inherited from the current search buffer rather than being the

Re: [PATCH] emacs: jump: sort-order bugfix

Mark Walters markwalters1...@gmail.com writes: default-value needs its argument to be quoted. --- Hi Mark, I really appreciate you sending in a bug fix. Thanks! I'd prefer to see the commit message describing the bug and the fix a bit. You do have some text here that would be a great

Re: [PATCH v1] emacs: `notmuch-search-find-stable-query-region' should never return an empty query.

Carl Worth cwo...@cworth.org writes: Mark Walters markwalters1...@gmail.com writes: Ok I now understand some of why it is a bug and it is a pretty gross mix: emacs does something odd, then notmuch-tag.c then xapian. It only happens in some cases: ... Anyway, I'm glad to see the notmuch emacs

Re: [PATCH v1] emacs: `notmuch-search-find-stable-query-region' should never return an empty query.

Mark Walters markwalters1...@gmail.com writes: Ok I now understand some of why it is a bug and it is a pretty gross mix: emacs does something odd, then notmuch-tag.c then xapian. It only happens in some cases: WARNING the following will archive some random messages: have a dump or backup or

Re: [PATCH 0/5] nmbug-status fixups from notmuch-to-html

W. Trevor King wk...@tremily.us writes: I've cherry-picked the three patches I liked from Carl's master [1,2] and added two cleanup commits of my own. I've left Carl's commit messages unchanged. I'm fine squashing my fixups into Carl's originals (leaving Carl as the author) if that's ok with

Re: [PATCH] nmbug-status: Make the footer's hr gray

W. Trevor King wk...@tremily.us writes: On Sun, May 11, 2014 at 12:08:10AM +0300, Tomi Ollila wrote: The rendered hr/ irritates me a bit, though. Maybe it could be colored light gray ? I can't reroll that one myself, unless Carl gives the ok. But here's some light-gray styling as an

Re: folder and path completely broken in HEAD?

dm-list-email-notm...@scs.stanford.edu writes: First, thanks for the response. The responsiveness and friendliness of the notmuch mailing list goes a long way towards compensating for any missing features / customizability one might want. I'm delighted to hear that the notmuch community

Re: folder and path completely broken in HEAD?

Jani Nikula j...@nikula.org writes: The discussions about this were lengthy and tedious, and I was glad we eventually reached some consensus about what we wanted. This much I do understand. And I apologize if I seem to be raising anew issues that should finally be behind us. Meanwhile, the

Re: Thanks for the nmbug-status program

W. Trevor King wk...@tremily.us writes: I think that making nmbug and nmbug-status generally applicable for other projects is a good target. I don't see any need to pull them out into a stand-alone project to do that though. For what it's worth, I don't disagree. Does that mean your

Re: Thanks for the nmbug-status program

Jani Nikula j...@nikula.org writes: On Wed, 23 Apr 2014, W. Trevor King wk...@tremily.us wrote: * f55ff7e Drop the --get-query option I'd like to keep the in-Git config, so I'm -1 here. FWIW I added the --get-query option as a convenience for accessing the queries from a nmbug companion

Re: Thanks for the nmbug-status program

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 W. Trevor King wk...@tremily.us writes: So, “here's a goal to shoot for, and I'm happy with my fork. If someone else wants to land patches like these upstream, I'm also happy dropping my fork.” ;). More just, Thanks for your code. I used it

Thanks for the nmbug-status program

Hi David, I just wanted to give you a quick thank you for the nmbug-status program. It's really handy to be able to publish decent-looking HTML pages based on notmuch search results with this. The script is quite general, (only a tiny portion was tied directly to nmbug), so I renamed it

Re: Thanks for the nmbug-status program

W. Trevor King wk...@tremily.us writes: http://git.cworth.org/git/notmuch-to-html Is there a clonable URL for this? Yes. Sorry I didn't provide that, (and clearly I need to reconfigure my git web pages to mention the URL): git clone http://git.cworth.org/git/notmuch-to-html I

Re: Thanks for the nmbug-status program

W. Trevor King wk...@tremily.us writes: $ git clone http://git.cworth.org/git/notmuch-to-html Sorry about that. What I had meant to say is: git clone git://git.cworth.org/git/notmuch-to-html (This time I actually copy-pasted from a terminal where I tested that the command actually

Re: [RFC PATCH] Re: excessive thread fusing

Austin Clements amdra...@mit.edu writes: But let me propose an idea I've been kicking around for a while: ghost message documents. Rather than using user metadata for tracking these missing messages, use regular documents with the exact same terms we use now for message IDs and thread IDs,

Re: [RFC PATCH] Re: excessive thread fusing

Mark Walters markwalters1...@gmail.com writes: I have done dome debugging of this. Thanks for looking closely, Mark! There is a patch below which fixes this test case but who knows what it breaks! Please DO NOT apply unless someone who knows this code says it's OK. I wrote much of the

[PATCH] emacs: notmuch-hello: Add variable to control order or saved-search results

This allows for the user to control the order that results are returned from saved-searches, (and independently from the order of all other searches which is controlled by notmuch-search-oldest-first). --- This allows me to get back to the behavior that notmuch had long ago, (the documentation

Re: [PATCH 0/5] lib: make folder: prefix literal

Austin Clements amdra...@mit.edu writes: Agreed. I believe this will also support MH, if I understand MH correctly (does anyone actually use MH?) When I started notmuch, I had all of my mail in one-message-per-file in various directories, (without these silly cur and new directories that

Re: [PATCH 0/5] lib: make folder: prefix literal

Jani Nikula j...@nikula.org writes: Unfortunately, I haven't had the time to experiment with this. But it bugs me that the probabilistic folder: prefix has stemming and it's case insensitive. It's possible to work around the stemming with the anchors you suggest or by quoting, but is there a

Re: [PATCH 0/5] lib: make folder: prefix literal

Jani Nikula j...@nikula.org writes: Here's a thought. With boolean prefix folder:, we can devise a scheme where the folder: query defines what is to be matched. I like the idea, but I tried to infer the rules from the examples, and I failed. It looks like there are two new symbols, / and /. but

Re: [PATCH] debian: package ruby bindings

Felipe Contreras felipe.contre...@gmail.com writes: My hypothetical laziness is not the reason. It was at the strong insistence of Carl that things are organized this way. I still don't see why we need to do that. The notmuch project shouldn't be bound to the debian project. I'm not sure

[PATCH] bitmap:improve memory usage using CHAR_BITS and unsigned CHAR

Robert Mast writes: > Re-submission for comment-reasons. Very nicely done, Robert. Thanks. -Carl (who's not quite merging patches again yet, but likely will be soon) -- carl.d.worth at intel.com -- next part -- A non-text attachment was scrubbed... Name: not available

Reply all - issue

Jameson Graef Rollins writes: > Just a thought: what if messages with a given tag (e.g. "new-thread") > were always treated as the source of a new thread? It's a good start. And an approach like that would have the advantage that one could undo a thread-split by just removing the tag. (That's

RE: Reply all - issue

Jameson Graef Rollins jroll...@finestructure.net writes: Just a thought: what if messages with a given tag (e.g. new-thread) were always treated as the source of a new thread? It's a good start. And an approach like that would have the advantage that one could undo a thread-split by just

[PATCH] convert bitmap to unsigned char

Robert Mast writes: > --- Hi Robert, It looks like the git exercise is proving useful. Keep it up! If you look through the git logs a bit you'll find that the overwhelming convention is for a commit message to have a single-line summary followed by a (potentially longer) expanded comment. The

Re: [PATCH] convert bitmap to unsigned char

Robert Mast beheer...@tekenbeetziekten.nl writes: --- Hi Robert, It looks like the git exercise is proving useful. Keep it up! If you look through the git logs a bit you'll find that the overwhelming convention is for a commit message to have a single-line summary followed by a (potentially

It's good to be "back"!

Elsewhere, in a non-hijacked thread, Carl Worth wrote: > Is there any existing thread-breaking? There wasn't the last time I > looked at the code closely, (but admittedly, that was a while ago). Hi folks, I've been away from any active involvement in the notmuch community for far to

Reply all - issue

Robert Mast writes: > Your point on patch-breaking related to gmail and my proposal isn't > completely clear to me, but I've probably addressed it well with my new > approach. The issue here is that many developers tend to develop a patch series (perhaps with dozens of patches) as a single

RE: Reply all - issue

Robert Mast beheer...@tekenbeetziekten.nl writes: Your point on patch-breaking related to gmail and my proposal isn't completely clear to me, but I've probably addressed it well with my new approach. The issue here is that many developers tend to develop a patch series (perhaps with dozens of

It's good to be back!

Elsewhere, in a non-hijacked thread, Carl Worth wrote: Is there any existing thread-breaking? There wasn't the last time I looked at the code closely, (but admittedly, that was a while ago). Hi folks, I've been away from any active involvement in the notmuch community for far too long

[PATCH] Restore original keybinding ('r' = reply-to-all)

Philip Hands writes: > I find the change to the new (only reply to sender) behaviour serously > irritating, because it seems I cannot train myself to hit R all the time > (which is pretty much what I always want). I'm in a similar camp. I tried (and failed) to adopt to the current mode, (once I

Re: [PATCH] Restore original keybinding ('r' = reply-to-all)

Philip Hands p...@hands.com writes: I find the change to the new (only reply to sender) behaviour serously irritating, because it seems I cannot train myself to hit R all the time (which is pretty much what I always want). I'm in a similar camp. I tried (and failed) to adopt to the current

[PATCH] Restore original keybinding ('r' = reply-to-all)

Since the beginning of time, the emacs interface provided a keybinding of 'r' to reply to a message, (and originally, all recipients). Then, before release 0.12 the emacs interface acquired a new reply-to-sender only feature. In commit f02b475fa781bb5df3358c73213e7633a99f016e the new feature was

[PATCH] Restore original keybinding ('r' = reply-to-all)

Since the beginning of time, the emacs interface provided a keybinding of 'r' to reply to a message, (and originally, all recipients). Then, before release 0.12 the emacs interface acquired a new reply-to-sender only feature. In commit f02b475fa781bb5df3358c73213e7633a99f016e the new feature was

notmuch git's disk is full! ERROR pushing.

On Sun, 08 Jan 2012 13:55:53 +0100, Sebastian Spaeth wrote: > Actually trying to push the above 2 patches, I get > > Writing objects: 100% (8/8), 1.25 KiB, done. > Total 8 (delta 5), reused 0 (delta 0) > error: unable to create temporary sha1 filename : No space left on > device My apologies!

Re: notmuch git's disk is full! ERROR pushing.

On Sun, 08 Jan 2012 13:55:53 +0100, Sebastian Spaeth sebast...@sspaeth.de wrote: Actually trying to push the above 2 patches, I get Writing objects: 100% (8/8), 1.25 KiB, done. Total 8 (delta 5), reused 0 (delta 0) error: unable to create temporary sha1 filename : No space left on device

Rethinking *_destroy()

On Mon, 19 Sep 2011 16:22:39 -0400, Ben Gamari wrote: > As many might have noticed, there was recently a bit of a discussion on > this list concerning the state of memory management in libnotmuch, > especially regarding some classes of garbage collectors. > > To summarize (someone correct me if

Re: Rethinking *_destroy()

On Mon, 19 Sep 2011 16:22:39 -0400, Ben Gamari bgamari.f...@gmail.com wrote: As many might have noticed, there was recently a bit of a discussion on this list concerning the state of memory management in libnotmuch, especially regarding some classes of garbage collectors. To summarize

Encodings

On Mon, 11 Jul 2011 16:04:17 +0200, Sebastian Spaeth wrote: > The answer is that things are very implicit. notmuch.h speaks of > strings but never mentions encodings Much of this was intentional on my part. For example, I intentionally avoided restrictions on what could be stored as a tag in

Re: Encodings

On Mon, 11 Jul 2011 16:04:17 +0200, Sebastian Spaeth sebast...@sspaeth.de wrote: The answer is that things are very implicit. notmuch.h speaks of strings but never mentions encodings Much of this was intentional on my part. For example, I intentionally avoided restrictions on what could be

[PATCH] NEWS: Add notes for (imminent) notmuch 0.6 release

By skimming through "git log 0.5..origin/release" late at night. Hopefully everything here is accurate. --- I've already pushed this out to master. David, obviously this is intended to be cherry-picked over to the release branch. And everyone, please review what I've written and provide any

[PATCH] emacs: Fix to unconditionally display subject changes in collapsed thread view

On Fri, 1 Jul 2011 02:01:08 -0700, Carl Worth wrote: > Rather than fixing the name of the variable and changing its default > value, here we remove the condition entirely, such that the feature is > enabled unconditionally. I've just pushed this change out. I emailed it here just t

[PATCH] emacs: Fix to unconditionally display subject changes in collapsed thread view

d) +Subject: [notmuch] What a great idea! Jan Janak (2009-11-17) (inbox) Carl Worth (2009-11-18) (inbox unread) -- 1.7.5.4

[PATCH] emacs: Fix to unconditionally display subject changes in collapsed thread view

a great idea! Jan Janak j...@ryngle.com (2009-11-17) (inbox) Carl Worth cwo...@cworth.org (2009-11-18) (inbox unread) -- 1.7.5.4 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch

Re: [PATCH] emacs: Fix to unconditionally display subject changes in collapsed thread view

On Fri, 1 Jul 2011 02:01:08 -0700, Carl Worth cwo...@cworth.org wrote: Rather than fixing the name of the variable and changing its default value, here we remove the condition entirely, such that the feature is enabled unconditionally. I've just pushed this change out. I emailed it here just

[PATCH] NEWS: Add notes for (imminent) notmuch 0.6 release

By skimming through git log 0.5..origin/release late at night. Hopefully everything here is accurate. --- I've already pushed this out to master. David, obviously this is intended to be cherry-picked over to the release branch. And everyone, please review what I've written and provide any

Re: [PATCH] remove prefixes from `--output={threads, messages}' results

On Thu, 30 Jun 2011 10:19:49 +0200, Pieter Praet pie...@praet.org wrote: Alter `do_search_threads()' and `do_search_messages()' to not prepend each result with `thread:' respectively `id:'. My one concern here is that I've sometimes had a message-id without the id prefix and run a command like

  1   2   3   4   5   6   7   8   9   10   >