public inbox for howm-eng@lists.osdn.me
 help / color / mirror / Atom feed
From: soy.el.gato.negro at gmail.com (Kenneth Wyatt)
Subject: [Howm-eng 164] Anybody having issues after upgrade to Emacs 27?
Date: Sun, 13 Sep 2020 19:55:03 +1000	[thread overview]
Message-ID: <55b54ceb-e0e8-8ed9-91cf-9c1dd7356cfd@gmail.com> (raw)

Hey guys.

Looks like this list has been pretty quiet for a few years based on the 
archive.

I've run into a little problem in the last few days, and the prime 
suspect is having just upgraded to Emacs 27.

I'm on Emacs 27.1 and howm 1.4.6.

I'm fairly certain the upgrade to Emacs 27 broke something. Howm does 
not seem able to search any of my files any longer. I have a file where 
I keep a list of important keywords with come-from link. Some of them 
will execute a search, some of them won't. The one's that won't simply 
report "No match." and their face is not my action-lock-face. For 
keywords displayed with the correct action-lock-face, when they are 
activated, I get a list of only the file which I have open, with the 
match being the come-from link itself.

If I do a (howm-list-all) my files are all there however.

I gave external grep a shot just to eliminate that variable, and it made 
no difference.

Anybody run into this issue? Is this just something about my config, or 
has something in Emacs 27 broken something fundamental here?

In the meantime I'm gonna see if I can compile an older version of 
Emacs, but I had to change a few things in my init to get 27 working., 
so we'll see if those changes are backwards compatible or if I then have 
to jump through further hoops.

Just looking to see if this is an isolated issue.

Cheers guys.

Kenneth


             reply	other threads:[~2020-09-13  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13  9:55 soy.el.gato.negro [this message]
2020-09-13 10:20 ` [Howm-eng 165] " soy.el.gato.negro
2020-09-13 10:37 ` [Howm-eng 166] " khi
2020-09-13 12:25   ` [Howm-eng 168] " khi

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=55b54ceb-e0e8-8ed9-91cf-9c1dd7356cfd@gmail.com \
    --to=howm-eng@lists.osdn.me \
    /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).