all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 3/5] build: Add 'emacs-build-system'
Date: Mon, 22 Jun 2015 20:59:16 +0300	[thread overview]
Message-ID: <87si9jsjyj.fsf@gmail.com> (raw)
In-Reply-To: <CAKrPhPNkOLzx8ex8O1Qb=HLZRo+=cNHiZFaPgnoenajMMNvorg@mail.gmail.com> (Federico Beffa's message of "Mon, 22 Jun 2015 10:51:51 +0200")

[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]

Federico Beffa (2015-06-22 11:51 +0300) wrote:

> On Sun, Jun 21, 2015 at 10:40 PM, Alex Kost <alezost@gmail.com> wrote:
>>> new file mode 100644
>>> index 0000000..da2b594
>>> --- /dev/null
>>> +++ b/guix/build-system/emacs.scm
>> [...]
>>> +                    #:tests? ,tests?
>>> +                    #:phases ,phases
>>> +                    #:outputs %outputs
>>> +                    #:search-paths ',(map search-path-specification->sexp
>>> +                                          search-paths)
>>> +                    #:inputs %build-inputs)))
>>> +
>> spaces on this line ^
>
> Hi, thanks for the review!
>
> This and other spaces that you indicate as "extra", are included by
> Emacs by pressing TAB. This is because, as an example, the above
> snippet finishes an internal define form and not a top-level form.

Then don't press TAB on an empty line if you are not going to write
something there :-)

> I'm following the Emacs behavior. Is there a convention to suppress
> all spaces (in spite of what Emacs does)?

Well, these trailing spaces are artifacts of (inaccurate) coding.  Emacs
can't read user's mind to decide if the spaces are redundant or
intended.

As Mathieu, I also use 'delete-trailing-whitespace' command when I want
to get rid of the whitespaces in the current buffer.  You may try to put
it into 'after-save-hook', but I would not do this as I don't like when
my files are edited without asking me.

Also I prefer to _see_ the trailing whitespaces.  For that I set
'show-trailing-whitespace' variable to t in "text" and "prog" buffers:


[-- Attachment #2: show-whitespaces.el --]
[-- Type: application/emacs-lisp, Size: 199 bytes --]

[-- Attachment #3: Type: text/plain, Size: 10 bytes --]


-- 
Alex

  parent reply	other threads:[~2015-06-22 17:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21  8:31 [PATCH 3/5] build: Add 'emacs-build-system' Federico Beffa
2015-06-21 20:40 ` Alex Kost
2015-06-22  8:51   ` Federico Beffa
2015-06-22 11:49     ` Mathieu Lirzin
2015-06-22 17:59     ` Alex Kost [this message]
2015-06-22 19:33       ` Federico Beffa
2015-06-22 19:40         ` Thompson, David
2015-06-23  6:51           ` Federico Beffa
2015-06-25 11:57             ` Ludovic Courtès
2015-06-25 18:39               ` Federico Beffa
2015-06-23 11:57         ` Alex Kost
2015-06-24 16:12           ` Federico Beffa
2015-06-25 12:33             ` Ludovic Courtès
2015-06-25 18:36               ` Federico Beffa
2015-06-27  9:59                 ` Ludovic Courtès
2015-07-06 17:47 ` Alex Kost
  -- strict thread matches above, loose matches on Subject: below --
2015-07-07  7:21 Federico Beffa
2015-07-07 16:58 ` Alex Kost
2015-07-08 20:22   ` Federico Beffa
2015-07-09  8:51     ` Alex Kost
2015-07-09 20:41       ` Federico Beffa
2015-07-10  6:47         ` Alex Kost
2015-07-10  7:43           ` Federico Beffa
2015-07-15 21:52           ` Ludovic Courtès

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=87si9jsjyj.fsf@gmail.com \
    --to=alezost@gmail.com \
    --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.