all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 27497@debbugs.gnu.org
Subject: [bug#27497] [PATCH] gnu: Add emacs-org-edit-latex.
Date: Thu, 29 Jun 2017 15:31:31 +0300	[thread overview]
Message-ID: <87o9t7asbg.fsf@gmail.com> (raw)
In-Reply-To: <0281e55d.AEQAMUGi-eAAAAAAAAAAAAPNhpIAAAACwQwAAAAAAAW9WABZVJZs@mailjet.com> (Arun Isaac's message of "Thu, 29 Jun 2017 11:25:50 +0530")

Arun Isaac <arunisaac@systemreboot.net> writes:

> Before pushing, I'm slightly modifying the synopsis and description as
> follows. I use org-mode and latex regularly, but haven't actually used
> this package. So, please let me know if my modification has not altered
> the meaning, and the text is still accurate. Once you confirm, I will
> push.
>
>     (synopsis "Edit a latex fragment just like editing a src block")
>     (description "@code{emacs-org-edit-latex} is an extension for org-mode.
> It lets you edit a latex fragment in a dedicated buffer just like editing a
> src block.")

Yes, it's meaningful.

But, "(description" must be on separate line, doesn't it?
Like in 2482c02f3b23b2490a6647e0717cf8a4ccf3f6a8

  parent reply	other threads:[~2017-06-29  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 10:52 [bug#27497] [PATCH] gnu: Add emacs-org-edit-latex Oleg Pykhalov
2017-06-26 13:23 ` Arun Isaac
     [not found] ` <9b1d4b50.AEEAMaYFajwAAAAAAAAAAAPNhpIAAAACwQwAAAAAAAW9WABZUQra@mailjet.com>
2017-06-26 17:36   ` Oleg Pykhalov
2017-06-28 21:46 ` Oleg Pykhalov
2017-06-29  5:55   ` Arun Isaac
     [not found]   ` <0281e55d.AEQAMUGi-eAAAAAAAAAAAAPNhpIAAAACwQwAAAAAAAW9WABZVJZs@mailjet.com>
2017-06-29 12:31     ` Oleg Pykhalov [this message]
2017-06-30 14:31       ` bug#27497: " Arun Isaac

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

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

  git send-email \
    --in-reply-to=87o9t7asbg.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=27497@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.