From: Pascal Bourguignon <spam@mouse-potato.com>
Subject: Re: Wrong type argument: integerp, nil
Date: Sat, 03 Dec 2005 19:31:48 +0100 [thread overview]
Message-ID: <87u0dqdobv.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: dmsnnb$f81$1$8302bc10@news.demon.co.uk
kevin bailey <kbailey@freewayprojects.com> writes:
> i'm editing files over FTP using standard debian sarge emacs21 on the
> console and i keep getting the system bell beeping and a message appearing
> saying
>
> Wrong type argument: integerp, nil
>
> messages on google groups all relate to email reading which i am not using
> emacs for.
>
> any pointers?
M-x set-variable RET debug-on-error RET t RET
Then do whatever you do to get the error again, and show us the
*Backtrace* buffer contents.
--
__Pascal Bourguignon__ http://www.informatimago.com/
In deep sleep hear sound,
Cat vomit hairball somewhere.
Will find in morning.
next prev parent reply other threads:[~2005-12-03 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 18:21 Wrong type argument: integerp, nil kevin bailey
2005-12-03 18:31 ` Pascal Bourguignon [this message]
2005-12-03 19:29 ` kevin bailey
2005-12-06 0:13 ` Kevin Rodgers
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=87u0dqdobv.fsf@thalassa.informatimago.com \
--to=spam@mouse-potato.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).