unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: emacs 22.1 on hp-ux 11.11 core dumps when DISPLAY not set
Date: Thu, 13 Sep 2007 23:00:09 -0400	[thread overview]
Message-ID: <ig4phygddy.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1ITXON-0003il-QK@fencepost.gnu.org> (Richard Stallman's message of "Fri, 07 Sep 2007 02:32:35 -0400")


Of the static uses I identified, five remain. I don't understand why
any of them need to be static, and I'm reluctant to change things I
don't understand. Which is better: leave them in function scope and
delete the `static', or move them to file scope?


fringe.c (init_fringe_bitmap) <swap_nibble>
gtkutil.c (xg_separator_p) <separator_names>
image.c  (our_memory_fill_input_buffer) <buffer>
         (gif_load) <interlace_start, interlace_increment>

  parent reply	other threads:[~2007-09-14  3:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1B2B2EF98D55CB41BD16F13B18B9B0080303EEB4@FFBRUE001.cfmu.corp.eurocontrol.int>
     [not found] ` <E1IShLe-0002kt-UF@fencepost.gnu.org>
     [not found]   ` <b8ejhdlvgn.fsf@fencepost.gnu.org>
2007-09-05 20:01     ` emacs 22.1 on hp-ux 11.11 core dumps when DISPLAY not set Richard Stallman
2007-09-06  7:04       ` Glenn Morris
2007-09-07  6:32         ` Richard Stallman
2007-09-07  7:05           ` Glenn Morris
2007-09-08  7:01             ` Richard Stallman
2007-09-12  1:32               ` Glenn Morris
2007-09-13 16:30                 ` Richard Stallman
2007-09-14  3:00           ` Glenn Morris [this message]
2007-09-14  6:28             ` Jan Djärv
2007-09-14  7:25               ` Glenn Morris
2007-09-15  2:09                 ` Richard Stallman
2007-09-15 19:50                   ` Glenn Morris
2007-09-15  8:04             ` Richard Stallman
2007-09-07  6:32         ` Richard Stallman
2007-09-12  7:31           ` Glenn Morris

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=ig4phygddy.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).