unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Willem Rein Oudshoorn <woudshoo@xs4all.nl>
To: emacs-devel@gnu.org
Subject: Re: package descriptive text and lm-commentary
Date: Sun, 04 Aug 2013 22:17:15 +0200	[thread overview]
Message-ID: <m1li4hb48k.fsf@xs4all.nl> (raw)
In-Reply-To: jwvk3k14afl.fsf-monnier+emacs@gnu.org

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Yesterday I created my first package, a single .el file.
>> Today I noticed that the description of the package, as shown in emacs
>> and on marmalade, lookes like:
>
>>    ;;; Commentary:
>
>>    ;; Text bla etce...
>
> Not sure what you mean.  http://marmalade-repo.org/packages/sparkline
> shows it without the ";;".

Hm, yes you are right.  I got confused with the few different places
I saw the package description.  So I checked again.

1 - On the web page of marmalade it is ok
2 - In emacs, the description with list-packages and showing the details
    has the ';;'
3 - If I use `package-upload-buffer' it will create a 
    sparkline-readme.txt also containing the ';;'.

It does not really matter but it bugs me.
Just for my information, I assume it is supposed to show without the
';;' for single file emacs packages right?  

>
>> 1 - lm-commentary
>
> lm-commentary is expected to return the text in all its ";;" glory, yes.
>
Ah, that is good to know.  


Well, if it keeps bugging me, I will try to figure out what goes wrong.

Also, I appreciate the time you took to check out the description.

Wim Oudshoorn.




  reply	other threads:[~2013-08-04 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04 11:17 package descriptive text and lm-commentary Willem Rein Oudshoorn
2013-08-04 17:47 ` Stefan Monnier
2013-08-04 20:17   ` Willem Rein Oudshoorn [this message]
2013-08-04 20:28     ` Stefan Monnier
2013-08-04 20:31       ` Willem Rein Oudshoorn

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=m1li4hb48k.fsf@xs4all.nl \
    --to=woudshoo@xs4all.nl \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

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

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).