Seems to have replaced the original on Arch. It's a breaking change; the triple-ticks in particular are now broken upon conversion.
My stacktrace looks the same as dilyn's.
I've added some data to the panic locally and it looks like my
Subcontext) is coming through as
-1for some reason.
I'm setting the
/usrwhen compiling. It's correctly propagating to make. I can see all the stuff in
/usr/share/aerc/but it doesn't find it unless I set the config explicitly in
I'm seeing the same behaviour with the
template-dirsoption, too. It doesn't seem to be checking the default directory (per the config manpage). Adding it to the config manually fixes it.
Not sure if this is an intentional change between 0.5.2 and master but
stylesets-dirsnow appears to be effectively a required property in the config. Without it you'll see:
Failed to load config: Unable to load default styleset: Can't find styleset "default" in any of [stylesets]
Another idea, inside
- Add new file
Then add a
synccommand to bangin that attempts to pull in those lists and put them into the appropriate directory. If we consider it like adblock lists then we don't really care about versioning.
I'm not sure how this would intersect with any attempts to simultaneously use some local lists. I think this only works with such a simple design if everything in the lists directory is wiped prior to syncing.
It needs to be possible to automate this process.
The simplest solution would be to add a new shell script, or patch support into the main script, for providing a URL from which we can attempt to get the list and place it in the right directory. This won't support versioning, though, unless we store a cache of where the data came from to look back upon later.
The most "correct" solution in my eyes is for banglists to be distributed in package managers, but... is this only viable on Arch? That'd be limiting.
I think this introduces an ambiguity issue where it can only work if we always interpret
!as a bang (rather than just the last as we do now).
a!bcdefgh!i, who's to say that
!bcdefghisn't a bang?
We could introduce a space separator, but then it starts to feel hacky and hard to remember...
Which'd output each bang's output to a newline.