all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: control@debbugs.gnu.org, Oleg Pykhalov <go.wigust@gmail.com>
Cc: tracker@debbugs.gnu.org, 39878@debbugs.gnu.org
Subject: [bug#39878] Processed: control message for bug #39878
Date: Wed, 29 Jul 2020 08:43:14 -0700 (PDT)	[thread overview]
Message-ID: <46b2caca-0cdd-42cc-bb1b-4d5041036709@default> (raw)
In-Reply-To: <handler.s.C.15959995592632.transcript@debbugs.gnu.org>

I just noticed this close message.  Didn't notice
the bug report before this.

I don't understand what the problem reported was.

(The file names were written wrong in the bug
report; dunno whether that's relevant.  There's no
"s" at the end of each base file name.  E.g., it's
bookmark+-mac.el, not bookmarks+-mac.el.)

Each Lisp file that needs `bookmark+-mac.el' for
its compilation has this at the beginning, to make
sure `bookmark+-mac.el' is loaded when byte-compiling:

(eval-when-compile
 (or (condition-case nil
         ;; Use load-library to ensure latest .elc.
         (load-library "bookmark+-mac")
       (error nil))
     ;; Require, so can load separately if not on `load-path'.
     (require 'bookmark+-mac)))

> Processing commands for control@debbugs.gnu.org:
> 
> > close 39878
> bug#39878: gnu: add emacs-bookmarks+
> bug closed, send any further explanations to
> 39878@debbugs.gnu.org and nly@disroot.org (Amar M. Singh)
> 
> > quit
> Stopping processing here.
> 
> Please contact help-debbugs@gnu.org if you need assistance.
> 
> GNU bugs database,
> https://urldefense.com/v3/__http://debbugs.gnu.org/__;!!GqivPVa7Brio!OA8tb25o
> mQdQHUL-s_aQrQ1a107RcffjZ7dxn_RqhAOl43oCyu9MCfkUCKRnMYwL$
> 




           reply	other threads:[~2020-07-29 16:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <handler.s.C.15959995592632.transcript@debbugs.gnu.org>]

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=46b2caca-0cdd-42cc-bb1b-4d5041036709@default \
    --to=drew.adams@oracle.com \
    --cc=39878@debbugs.gnu.org \
    --cc=control@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    --cc=tracker@debbugs.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.