unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Re: Number of open buffers?
Date: 20 Nov 2003 22:15:14 +0100	[thread overview]
Message-ID: <x54qwykahp.fsf@lola.goethe.zz> (raw)
In-Reply-To: bpja4e$89m$1@pita.alt.net

Ignoramus1904 <ignoramus1904@NOSPAM.1904.invalid> writes:

> In article <m31xs2c3na.fsf@localhost.localdomain>, Micah Cowan wrote:
> > Ignoramus1904 <ignoramus1904@NOSPAM.1904.invalid> writes:
> > 
> >> Eli Zaretskii wrote:
> >> >> From: Ignoramus1904 <ignoramus1904@NOSPAM.1904.invalid>
> >> >> 
> >> >> I want to modify it so that if the # of open file buffers is more than
> >> >> one, emacs would ask YES/NO, if less, I exit. I am a very bad lisp
> >> >> programmer, any suggestions?
> >> > 
> >> > 
> >> > For a more bullet-proof code, walk the buffer list returned by the
> >> > function buffer-list, and filter out any buffer which doesn't have a
> >> > file associated with it (its buffer-file-name will be nil).  What is
> >> > left are the buffers which visit files.
> >> > 
> >> 
> >> Thanks Eli, sounds a little bit above my head to be honest. I do C++
> >> and Perl and do not know Lisp well. I just thought that there was a
> >> function like get-number-of-file-buffers, or something like that.
> > 
> > The following is what he's talking about, I think:
> > 
> > (defun get-number-of-file-buffers ()
> >   (interactive)
> >   (let (num)
> >     (setq num 0)
> >     (dolist (buf (buffer-list))
> >       (when (buffer-file-name buf)
> >           (setq num (+ num 1))
> >       ))
> >     num
> >     )
> >   )

Somewhat shorter:

(defun get-number-of-file-buffers ()
  (interactive)
  (let ((num 0))
    (dolist (buf (buffer-list) num)
      (when (buffer-file-name buf)
          (setq num (1+ num))))))

> Thanks. When I try to run it via eval-expr, saying
> 
> (insert get-number-of-file-buffers)
> 
> It says: Error: void-variable. Data: get-number-of-file-buffers

Yes.  One calls a function by putting it after an opening
parenthesis.  The way you tried to "call" it, just a variable of that
name got referenced, and there is no such variable.  In addition, the
function returns a numeric expression, and `insert' expects a string.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  parent reply	other threads:[~2003-11-20 21:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bpilkc$pq1$0@pita.alt.net>
2003-11-20 16:19 ` Number of open buffers? Eli Zaretskii
     [not found] ` <mailman.342.1069348789.399.help-gnu-emacs@gnu.org>
     [not found]   ` <bpirf4$8ee$2@pita.alt.net>
2003-11-20 18:10     ` Micah Cowan
     [not found]       ` <bpja4e$89m$1@pita.alt.net>
2003-11-20 21:15         ` David Kastrup [this message]
2003-11-20 21:50           ` lawrence mitchell
2003-11-20 22:14             ` David Kastrup
2003-11-20 22:46               ` lawrence mitchell
2003-11-20 23:40                 ` David Kastrup
2003-11-20 22:42           ` Johan Bockgård
2003-11-20 21:43         ` Lucas
     [not found]         ` <mailman.369.1069368465.399.help-gnu-emacs@gnu.org>
     [not found]           ` <bplam3$nrj$1@pita.alt.net>
2003-11-21 15:36             ` David Kastrup
2003-11-21 15:52           ` Stefan Monnier
2003-11-21 20:21             ` Lucas

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=x54qwykahp.fsf@lola.goethe.zz \
    --to=dak@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.
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).