Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: emacs23 broken on master (gnus-compat problems)
Date: Sat, 04 Feb 2012 10:51:38 +0100	[thread overview]
Message-ID: <87ehubvsd1.fsf@dod.no> (raw)

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

Platform: Ubuntu 10.0
          GNU Emacs 23.1.1


Offending commit (found with git bisect):

sb@aa1steinar:~/git/gnus$ git bisect good
15ceddb656d3650b6626205b58629b68f67a86c3 is the first bad commit
commit 15ceddb656d3650b6626205b58629b68f67a86c3
Author: Lars Ingebrigtsen <larsi@gnus.org>
Date:   Wed Feb 1 20:35:34 2012 +0100

    Redefine `delete-directory' on Emacs 22 and XEmacs
    
    * gnus-compat.el: Redefine `delete-directory' to provide recursive
    deletion unless already defined.

:040000 040000 18a8200b49ff2ab3b61147f7cb13e8e61eff47c9 c3d857de599cade1098d29888c55e4b0c9cdf93a M	lisp


Stack trace:


[-- Attachment #2: Stack trace from starting gnus --]
[-- Type: text/plain, Size: 1394 bytes --]

Debugger entered--Lisp error: (wrong-type-argument sequencep t)
  byte-code("ÂψÅ!„\0Æ!ƒ\0Å\"ˆÉ!GUƒ4Ë\bBÌ!„/ÍÉK\"ˆÉ\"ˆÐ!‡" [current-load-list nil (byte-code "Á!‡" [require help-fns] 2) ((error)) fboundp help-function-arglist function-arglist defalias #[(def &optional preserve-names) "Â\b!—!@A‡" [def read-from-string function-arglist] 3 "Return a formal argument list for the function DEF.\nPRESERVE-NAMES is ignored."] delete-directory 1 gnus-compat-original-delete-directory default-boundp set-default #[(directory &optional recursive trash) "\b„\b	\n!‡\n\"^[‰ƒ7\f@È\v!ɝ„0Ê\v!ƒ,Ë\v\"ˆ‚0Ì\v!ˆ\fA‰„\0*\n!‡" [recursive gnus-compat-original-delete-directory directory file --cl-dolist-temp-- directory-files t nil file-name-nondirectory ... file-directory-p delete-directory delete-file] 4 "Delete the directory named DIRECTORY.  Does not follow symlinks.\nIf RECURSIVE is non-nil, all files in DIRECTORY are deleted as well.\nTRASH is ignored." "DDirectory: "] provide gnus-compat] 3)
  require(gnus-compat)
  eval-buffer(#<buffer  *load*> nil "/home/sb/git/gnus/lisp/gnus.el" nil t)  ; Reading at buffer position 1237
  load-with-code-conversion("/home/sb/git/gnus/lisp/gnus.el" "/home/sb/git/gnus/lisp/gnus.el" nil nil)
  load("gnus.el")
  load-library("gnus.el")
  call-interactively(load-library t nil)
  execute-extended-command(nil)
  call-interactively(execute-extended-command nil nil)

             reply	other threads:[~2012-02-04  9:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04  9:51 Steinar Bang [this message]
2012-02-06 23:44 ` Lars Ingebrigtsen
2012-02-06 23:48   ` Lars Ingebrigtsen
2012-02-07  6:06     ` Steinar Bang
2012-02-07 10:14       ` Steinar Bang
2012-02-07 20:29       ` Lars Ingebrigtsen
2012-02-07 20:52         ` Steinar Bang
2012-02-07 20:57           ` Steinar Bang
2012-02-07 21:03             ` Steinar Bang
2012-02-07 21:20               ` Steinar Bang
2012-02-07 21:39                 ` Andreas Schwab
2012-02-07 21:49                   ` Lars Ingebrigtsen
2012-02-07 21:39                 ` Lars Ingebrigtsen
2012-02-07 21:58                   ` Steinar Bang
2012-02-07 20:53         ` Andreas Schwab
2012-02-07 21:38           ` Lars Ingebrigtsen
2012-02-08  0:34       ` Carson Chittom
2012-02-07  6:01   ` Steinar Bang

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=87ehubvsd1.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).