From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] where did the processEffects switch go?
Date: Mon, 27 Nov 2017 01:26:29 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1711270111140.29508@carhart.net> (raw)
Wow, here I thought I knew several of the C files pretty well, but I
haven't been in for a while. Could you give me a pointer for where I
can find the new replacement for what processEffects used to do? Do we
still traverse a series of code letters for different types of effects?
I grepped around for several things but wasn't successful.
The thing I was trying to pursue in particular is eb$newLocation and
whether this can be used to give a clue about hash changes, which could
help fixing RC.
Thank you, I appreciate it :)
Kevin
reply other threads:[~2017-11-27 9:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LRH.2.03.1711270111140.29508@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.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).