all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: Guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>,
	Federico Beffa <beffa@ieee.org>
Subject: Re: [PATCH 6/6] gnu: Add emacs-slime.
Date: Fri, 1 Jan 2016 16:04:35 +0100	[thread overview]
Message-ID: <87r3i19w8s.fsf@mdc-berlin.de> (raw)
In-Reply-To: <56863A6B.90809@uq.edu.au>


Ben Woodcroft <b.woodcroft@uq.edu.au> writes:

> On 01/01/16 18:25, Ricardo Wurmus wrote:
>> Alex Kost <alezost@gmail.com> writes:
>>
>>> Ricardo Wurmus (2015-12-31 12:52 +0300) wrote:
>>>
>>>> Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
>>>>
>>>>> Do you know though, is there any way to get emacs to insert the extra
>>>>> space in description strings and comments automatically (without it
>>>>> messing things up of course). Perhaps we should modify the importers to
>>>>> insert this automatically in the description field.
>>>> The CRAN and Bioconductor importers already do this.  See
>>>> “beautify-description” in “guix/import/cran.scm”.
>>> Hm, is it reliable?  Not all dots specify an end of a sentence: there
>>> are things like "e.g.", "i.e.", "etc.".  Also there may be abbreviations
>>> like "ATA S.M.A.R.T. reading and parsing library" (synopsis of
>>> 'libatasmart' package).  Or even things like “<form> ... </form>”
>>> (description of 'perl-html-form') — it should probably be wrapped in
>>> @code{} by the way.
>> It’s not supposed to be maintenance-free.  Descriptions often start with
>> sentence fragments, which cannot be detected easily.  I found that
>> “beautify-description” works well enough to make packaging R stuff much
>> simpler for me.
>
> I'd like to add this to the Ruby importer. Do you think it is a good 
> idea to make your beautify-description available in import/utils ?

I think it could be generally useful to have something like that for all
importers.  Do you want to prepare a patch?

~~ Ricardo

  reply	other threads:[~2016-01-01 15:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 17:33 [PATCH 6/6] gnu: Add emacs-slime Federico Beffa
2015-12-31  0:55 ` Ben Woodcroft
2015-12-31  9:12   ` Federico Beffa
2016-01-05 22:17     ` Ludovic Courtès
2016-01-09 10:30       ` Federico Beffa
2016-01-09 15:27         ` Alex Kost
2016-01-09 18:45         ` Ludovic Courtès
2015-12-31  9:52   ` Ricardo Wurmus
2015-12-31 23:52     ` Alex Kost
2016-01-01  8:25       ` Ricardo Wurmus
2016-01-01  8:35         ` Ben Woodcroft
2016-01-01 15:04           ` Ricardo Wurmus [this message]
2016-01-05 14:25             ` [PATCH] import: Move beautify description from cran to utils. (was Re: [PATCH 6/6] gnu: Add emacs-slime.) Ben Woodcroft
2016-01-10 21:17               ` Ludovic Courtès
2016-01-14  9:49                 ` Ben Woodcroft
2016-01-14 10:31                   ` Ricardo Wurmus
2016-01-14 10:53                     ` Ben Woodcroft
2016-01-14 11:30                       ` Ricardo Wurmus
2016-01-14 12:15                         ` Ben Woodcroft
2016-01-17  1:00                           ` [PATCH] import: Move beautify description from cran to utils Ben Woodcroft
2016-01-18  9:45                             ` Ludovic Courtès
2016-01-20 22:13                               ` Ben Woodcroft
2016-01-21  8:51                                 ` Ludovic Courtès
2015-12-31 10:17 ` [PATCH 6/6] gnu: Add emacs-slime Alex Kost
2015-12-31 10:32   ` Federico Beffa
2015-12-31 20:40     ` Alex Kost
2015-12-31 10:33 ` Alex Kost

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=87r3i19w8s.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=alezost@gmail.com \
    --cc=b.woodcroft@uq.edu.au \
    --cc=beffa@ieee.org \
    --cc=guix-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 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.