From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] emacs-24 r117559: Fix bug #18636 with documentation of multi-monitor displays. Date: Sat, 11 Oct 2014 09:51:37 +0200 Message-ID: <87k3472gdy.fsf@fencepost.gnu.org> References: <83vbnuib0y.fsf@gnu.org> <83oatlitqk.fsf@gnu.org> <83mw95b1qy.fsf@gnu.org> <5bwq89f86w.fsf@fencepost.gnu.org> <83iojtazxc.fsf@gnu.org> <87ppe13smb.fsf@fencepost.gnu.org> <87lhop3p9q.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1413015797 9819 80.91.229.3 (11 Oct 2014 08:23:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 11 Oct 2014 08:23:17 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 11 10:23:14 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XcrxI-00035N-Ur for ged-emacs-devel@m.gmane.org; Sat, 11 Oct 2014 10:23:13 +0200 Original-Received: from localhost ([::1]:53362 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcrxI-0008E0-Hm for ged-emacs-devel@m.gmane.org; Sat, 11 Oct 2014 04:23:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43387) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xcrx3-0008Dk-Gk for emacs-devel@gnu.org; Sat, 11 Oct 2014 04:22:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xcrwz-00055b-5g for emacs-devel@gnu.org; Sat, 11 Oct 2014 04:22:57 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:43167) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xcrwz-00055Q-2o for emacs-devel@gnu.org; Sat, 11 Oct 2014 04:22:53 -0400 Original-Received: from localhost ([127.0.0.1]:50340 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xcrwr-0004LH-Oa; Sat, 11 Oct 2014 04:22:46 -0400 Original-Received: by lola (Postfix, from userid 1000) id 7C7DEE0DB0; Sat, 11 Oct 2014 09:51:37 +0200 (CEST) In-Reply-To: (Richard Stallman's message of "Fri, 10 Oct 2014 21:14:09 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:175252 Archived-At: Richard Stallman writes: > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > It might be good to create a Texinfo command that is like @example > but treats braces as ordinary characters. @verbatim is more or less like that, or at least you can combine it with @quote. Due to its implementation in TeX, it cannot really be used as a building block for macros you define yourself. It's only useful as a direct user input command. > Lilypond could define @lilypond an alias for that command. Since lilypond-book (the application converting files with @lilypond commands in them into proper Texinfo input) needs to insert the @image commands pointing to the graphics from processing the content in the @lilypond command into the actually generated Texinfo input, Texinfo does not get to see the original environment anyway. The actually generated input already uses @verbatim and looks something like @exampleindent 0 @verbatim bass = { \clef bass g4 b, c d e d8 c d2 } continuo = \figuremode { <_>4 <6>4 <5/>4 \override Staff.BassFigureAlignmentPositioning.direction = #UP %\bassFigureStaffAlignmentUp < _+ >4 <6> \set Staff.useBassFigureExtenders = ##t \override Staff.BassFigureAlignmentPositioning.direction = #DOWN %\bassFigureStaffAlignmentDown <4>4. <4>8 <_+>4 } \score { << \new Staff = bassStaff \bass \context Staff = bassStaff \continuo >> } @end verbatim @noindent @ifinfo @image{34/lily-fdcff975,,,[image of music],} @end ifinfo @html

[image of music]

@end html @iftex @include 34/lily-fdcff975-systems.texi @end iftex Richard, if you treat every example of a working system that somebody brings up in the course of a discussion as a request for letting you redesign stuff that has been working for decades to the satisfaction of its users rather than as input to the discussion, the discussion can go nowhere. It's fine to explore possible fundamental deficiencies and its effects on system and users concerning the aspects under discussion, but when some particular tangent has veered off completely from the topic of discussion and the list, it would make sense to continue it, if at all, in private communication. -- David Kastrup