> From: Robert Weiner <[email protected]> > Date: Mon, 4 Jul 2016 17:21:58 -0400 > Cc: Gavin Smith <[email protected]>, [email protected] > > On Sun, Jul 3, 2016 at 11:25 AM, Eli Zaretskii <[email protected]> wrote: > > the result [of using braces around key sequences in Info manuals) will > > confuse the reader > > This is an assumption you are making that has not been borne out by the > experience of users of these manuals > throughout the years.
Does my experience of 30 years of reading Info manuals count? We can ask RMS to provide a second opinion. > Prior to this discussion here, we have never heard from a single user about > any problems with this notation That can be explained in several ways that have nothing to do with the notation. > As you have said before regarding Emacs features, since it has been working a > certain way for years (with > my packages), until a better, more consistent techinque is proposed, I will > stay with this and let the users say > whether it is an issue or not. And again, maybe you will look at it and try > it out before dismissing it. My point is that if this is a better method, the entire Texinfo system should switch to it, rather than doing this in the manuals of a single project. > 1. The display is consistent across .pdf, .html and .info outputs. The same > markup can be used within any > standard text as well (similar to what markdown does and we know how popular > that is). Texinfo explicitly doesn't attempt to do this, since the capabilities of the various output formats are so different. > 2. Hyperbole recognizes global key sequences surrounded by braces and can > activate their key bindings > when selected with the mouse (or via a keyboard key). This is great for demos > or for frequently accessed long > sequences that may be hard to remember. Any reasons Hyperbole couldn't be taught to recognize any other format, including the standard Texinfo one? If not, does that mean Hyperbole doesn't support key sequences documented by other GNU packages?
