On Fri, Jul 17, 2026, at 2:59 AM, Devon H. O'Dell wrote: > ISTM the problem is that you want broadcast semantics for some things > (e.g., opening an image with page) and directed semantics for others (e.g., > sending a manpage to the acme that clicked). Would it be worth adding > semantics to caller and rules to allow a caller to specify it specifically > is interested in the result, and have rules that match if the caller > specifies the desire? > > There are a lot of individual ways to solve the specific issue of manpages, > but they don't seem to work generally without this.
If this were implemented, I'm sure some people would make good use of it. Personally though, I find situations where the source of data or even type of file are no help in determining where I want a file opened. I got some use out of private plumbers, sometimes with additional acme instances, sometimes with sub-rios, depending on project. I occasionally ran a sub-rio without a private plumber, but never acme. Running a second acme instance without its own plumber was just a nuisance. These days, I open what I want where I want on a case-by-case basis by various means, usually shell scripts and functions, sometimes scriptable applications and file managers. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb77bce4699e6922a-M0f46fca897e6f45dd0bae942 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
