unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: Mysterious backslash in menu-bar-make-toggle.
Date: Thu, 9 Jun 2005 16:47:15 -0500 (CDT)	[thread overview]
Message-ID: <200506092147.j59LlFj01635@raven.dms.auburn.edu> (raw)

I assume that the backslash removed by the patch below is a typo or the
result of confusion.  I am just checking to make sure that this is the
case.  I can install the patch if desired.  The backslash leads to
very bad looking docstrings.  Just do `C-h f toggle-debug-on-error RET'.
This produces:

toggle-debug-on-error is an interactive compiled Lisp function in `menu-bar'.
It is bound to <menu-bar> <options> <debug-on-error>.
(toggle-debug-on-error &optional interactively)

Toggle whether to enter Lisp debugger when an error is signaled.In an interactive call, record this option as a candidate for saving
by "Save Options" in Custom buffers.

===File ~/menu-bar-diff=====================================
*** menu-bar.el	21 Apr 2005 07:56:06 -0500	1.258
--- menu-bar.el	09 Jun 2005 15:21:59 -0500	
***************
*** 606,612 ****
    `(progn
       (defun ,name (&optional interactively)
         ,(concat "Toggle whether to " (downcase (substring help 0 1))
! 		(substring help 1) ".\
  In an interactive call, record this option as a candidate for saving
  by \"Save Options\" in Custom buffers.")
         (interactive "p")
--- 606,612 ----
    `(progn
       (defun ,name (&optional interactively)
         ,(concat "Toggle whether to " (downcase (substring help 0 1))
! 		(substring help 1) ".
  In an interactive call, record this option as a candidate for saving
  by \"Save Options\" in Custom buffers.")
         (interactive "p")
============================================================

                 reply	other threads:[~2005-06-09 21:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200506092147.j59LlFj01635@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    /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).