From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: setting local variables Date: Wed, 06 Sep 2017 09:33:53 -0700 Message-ID: <87y3pr7pn2.fsf@ericabrahamsen.net> References: <871sotiqld.fsf@ericabrahamsen.net> <87r2wsly88.fsf@nicolasgoaziou.fr> <877eykbpho.fsf@ericabrahamsen.net> <87wp5dmkm0.fsf@gmx.us> <87h8wh13tm.fsf@ericabrahamsen.net> <87y3psp5ne.fsf@gmx.us> <87mv68159v.fsf@nicolasgoaziou.fr> <87h8wgov62.fsf@gmx.us> <87fuc0asaq.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51678) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dpdHS-0006uR-B0 for emacs-orgmode@gnu.org; Wed, 06 Sep 2017 12:34:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dpdHM-0006SQ-1A for emacs-orgmode@gnu.org; Wed, 06 Sep 2017 12:34:22 -0400 Received: from [195.159.176.226] (port=42509 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dpdHL-0006OY-Pr for emacs-orgmode@gnu.org; Wed, 06 Sep 2017 12:34:15 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dpdH7-0005CQ-UU for emacs-orgmode@gnu.org; Wed, 06 Sep 2017 18:34:01 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Nicolas Goaziou writes: > Rasmus writes: > >> I could not get it to work. I tried stuff like "[[(org) Tables]]", >> "[[*(org) Tables]]" and , [[texinfo:(org) tables]]. > > You are talking about a special case for cross-referencing (which could > include internal reference, URL referencess). This is the job of > "org-info.el": > > [[info:org#tables]] I think I ran into trouble just doing a simple `org-store-link' from an Info file, then `org-insert-link' in the Org mode manual. That produced: [[info:org#Installation][info:org#Installation]] --> @ref{Installation,@ref{Installation,,,org,},,org,} --> *note *note (org)Installation::: (org)Installation. Of course, I should have edited the description part of the link: [[info:org#Installation][Installation]] --> @ref{Installation,Installation,,org,} --> *note Installation(org). Much better. I did once manage to produce a link that didn't follow to its destination, I think just using org-store|insert-link, but of course now can't reproduce. Anyway, I don't know if the above is actually a bug or not. [...] >> That is why I asked for a reference as I do not remember having seen such >> a layout in an info page. If we know of an example, it might not be hard >> to implement. > > The problem is not implementing it, really. It is about finding a way to > integrate it with Org syntax. > > "org.texi" uses a lot of "@subheading" and related. See for example > > (info "(org) Installation") > > "Using Emacs packaging system", "Downloading Org as an archive" and > "Using Org's git repository" are three examples of such layout. Why not just change the behavior of `org-export-headline-levels' for texinfo output? We can already make plain lists, it doesn't seem useful to me to also turn minor headings into lists. Since texinfo has the concept of pages, why not just inline headings below H: level? [...] > The manual is not targeted to Texinfo experts. The difference between > @ref arguments are subtle. At this point, I suggest to generate some > template with Org and tweak the result. I agree that Org doesn't need to support all the subtleties, but I did find the out-of-the-box `org-store|insert-link' pretty confusing. [...] > IMO, advanced marking is not needed, at least out of the box. For > example, @kbd{M-@key{TAB}} in Texinfo is morally equivalent to > ~M-~ in Org, as long as the document targets info. Morally equivalent in that they're typeset the same, right? I decided to embrace texinfo pedantry and make a kbd macro :) > Patch welcome! > > Also, two emphasis markers are unused in "ox-texinfo.el": _..._ and > +...+. Another solution would be to use them for Texinfo special markup. > However, it feels awkward to provide this by default. I'd be happy to provide a patch, and I think we should mention `org-texinfo-text-markup-alist', as well. Then we can say "here's how Org's basic markup elements are translated, here's a defcustom you can play with, and failing that you can also make a macro". To be honest I don't know how the markup alist is supposed to work, though. If I mark up a phrase /like so/, shouldn't that count as "italic", and get transformed into @emph{like so}? Right now it goes through unchanged into the Info file, which doesn't seem right, since the Texinfo manual seems to indicate that _this_ is the proper way to do emphasis. The other thing I'd like to expand is the "Plain lists in Texinfo export" section. First of all, it's about definition lists, not plain lists, which I found confusing. Also, I think it just needs to have more basic information in it, unless you already know texinfo well, it's hard to know what it's telling you. Eric