unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: C-z (Re: Two GTK related feature requests)
Date: Mon, 27 Oct 2003 12:46:04 +0000 (UTC)	[thread overview]
Message-ID: <m1AE6l2-000UNaC@rattlesnake.com> (raw)
In-Reply-To: <E1AE1OS-0007PL-AG@fencepost.gnu.org> (message from Richard Stallman on Mon, 27 Oct 2003 02:02:24 -0500)

   what else useful could we put on c-z
   instead of iconify?  it wd not be available on text terminals.

One possibility is to make it a prefix reserved for users,
like C-c followed by a letter.

For example, someone might bind keys to to show syslog using
live-find-file, to remove text properties that are visible in a
window, or to list and kill processes.

[These can  be derived from

    (defun remove-window-text-properties ()
      "Remove facemenu-created text properties visible in window."
      (interactive)
      (facemenu-remove-all (window-start) (window-end)))

    (defun show-syslog ()
      "Show the syslog using live-find-file.
    You and/or the file must have the correct permissions."
      (interactive)
      (let ((log-buffer (get-file-buffer "/var/log/syslog")))
        (cond (log-buffer (switch-to-buffer log-buffer))
              ((file-readable-p "/var/log/syslog")
               (live-find-file "/var/log/syslog"))
              (t (error "syslog file not readable by user `%s'"
                        (user-real-login-name))))))

and Kyle Jones' 1989 `vkill.el', or something more recent.]

-- 
    Robert J. Chassell                         Rattlesnake Enterprises
    http://www.rattlesnake.com                  GnuPG Key ID: 004B4AC8
    http://www.teak.cc                             bob@rattlesnake.com

  parent reply	other threads:[~2003-10-27 12:46 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  4:09 Two GTK related feature requests Simon Josefsson
2003-10-21  4:17 ` Masatake YAMATO
2003-10-21  4:27   ` Simon Josefsson
2003-10-22  9:25 ` Richard Stallman
2003-10-22 12:04   ` Simon Josefsson
2003-10-22 12:39     ` Luc Teirlinck
2003-10-22 13:44       ` Simon Josefsson
2003-11-02 19:34         ` Jan D.
2003-10-23  2:08   ` Michael Welsh Duggan
2003-10-25 20:08     ` James H.Cloos Jr.
2003-10-26  4:10       ` C-z (Re: Two GTK related feature requests) Karl Eichwalder
2003-10-26  6:11         ` Eli Zaretskii
2003-10-26  8:01           ` Karl Eichwalder
2003-10-27  7:02             ` Richard Stallman
2003-10-27 12:22               ` Kim F. Storm
2003-10-27 12:46               ` Robert J. Chassell [this message]
2003-10-27 14:05                 ` Kim F. Storm
2003-10-27 18:08                   ` Karl Eichwalder
2003-10-27 22:16                   ` Robert J. Chassell
2003-10-27 15:47                 ` C-z Werner LEMBERG
2003-10-27 16:36                 ` C-z (Re: Two GTK related feature requests) Juri Linkov
2003-10-27 19:44                   ` Kevin Rodgers
2003-10-28 20:39                 ` Richard Stallman
2003-10-29  7:01                   ` Karl Eichwalder
2003-10-29  7:28                     ` Miles Bader
2003-10-30  4:19                       ` Richard Stallman
2003-10-29  9:43                     ` David Kastrup
2003-10-29 13:30                     ` Stefan Monnier
2003-10-29 14:03                       ` Eli Zaretskii
2003-10-29 16:00                     ` Luc Teirlinck
2003-10-26 19:01         ` Stefan Monnier
2003-10-26 21:06           ` Miles Bader
2003-10-27  5:50             ` Eli Zaretskii
2003-10-27  6:46               ` Miles Bader
2003-10-27 16:55                 ` Juri Linkov
2003-10-28  2:01                   ` Miles Bader
2003-10-29 14:15           ` Stephan Stahl
2003-10-29 15:29             ` David Kastrup
2003-11-17 20:40   ` Two GTK related feature requests Kai Grossjohann
2003-11-18 23:03     ` Richard Stallman
2003-11-19 21:43       ` tabs proposal Alex Schroeder
2003-11-21  4:08         ` Richard Stallman

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=m1AE6l2-000UNaC@rattlesnake.com \
    --to=bob@rattlesnake.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.
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).