unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Documentation of latex style functions
Date: Sat, 30 Dec 2023 19:05:22 +0000	[thread overview]
Message-ID: <36kPt1zy6PyprSYlw8AjSIKralhz6R0Dr8cX1l3GOde1ygi8FsWY2CWHSHwDRGQvx0_QTqsCNOb93fWfCIhCmrHg3kOS2YNawQ_qeyLNRqc=@protonmail.com> (raw)
In-Reply-To: <875y0gjy54.fsf@dataswamp.org>


On Saturday, December 30th, 2023 at 1:07 PM, Emanuel Berg <incal@dataswamp.org> wrote:

> Heime wrote:
> 
> > I would like to display some documentation for the Latex
> > Style Functions directly from Emacs. What possibilities are
> > there to do such a thing ?
> 
> 
> I think this is a good starting point
> 
> https://www.emacswiki.org/emacs/LaTeX
> 
> As a side note, here is my modest contribution to the
> Emacs/LaTeX world. I actually did a lot of LaTeX from Emacs
> but only such small configuration and extension.
> Probably a good thing!
> 
> https://dataswamp.org/~incal/emacs-init/latex.el
> 
> But nothing to address your specific desire.

What I have done is to make a .el file with functions that can
be called to show documentation information.  Like so. 

Would you have some suggestions upon improvements ?

(defconst FirZp-vaj-doc
  "
 \\NewDocumentCommand {\\FirZp} { s O{blue} O{it} m }

 \\FirZp [FIR-KLR] [FIR-SHP] {FIR-KWD}

 Let FIR-KLR Colour
     FIR-SHP Shape {it,rm}
     FIR-KWD Keyword
")


(defun FirZp-vaj ()

  ;; Print documentation about \FirZp.
  (:documentation
   (concat
     FirZp-vaj-doc)))

 
> I did more for Bibtex tho,
> 
> https://dataswamp.org/~incal/emacs-init/bibtex/
> 
> but again nothing up the on-the-fly documentation alley.
> 
> --
> underground experts united
> https://dataswamp.org/~incal



      reply	other threads:[~2023-12-30 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30  0:50 Documentation of latex style functions Heime
2023-12-30  1:07 ` Emanuel Berg
2023-12-30 19:05   ` Heime [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='36kPt1zy6PyprSYlw8AjSIKralhz6R0Dr8cX1l3GOde1ygi8FsWY2CWHSHwDRGQvx0_QTqsCNOb93fWfCIhCmrHg3kOS2YNawQ_qeyLNRqc=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=incal@dataswamp.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).