unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Jacob Gerlach <jacobgerlach@gmail.com>,
	Sergey Ivanes <sergey.ivanes@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: RE: DELETE/C-h confusion
Date: Sun, 27 Jul 2014 18:13:37 -0700 (PDT)	[thread overview]
Message-ID: <e0e5741c-a0cd-4931-a5ea-d02d8f02d298@default> (raw)
In-Reply-To: <CAA6UvuFn=LqVTfx0fiJ-vLj9T2Y43T54rm2t+Pf1_r09u_e=Bg@mail.gmail.com>

http://stackoverflow.com/q/24986066/729907

Hopefully someone can help Sergey more than I was able to.
(Perhaps someone with a Mac?)



      reply	other threads:[~2014-07-28  1:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27 22:22 DELETE/C-h confusion Sergey Ivanes
2014-07-28  1:02 ` Jacob Gerlach
2014-07-28  1:13   ` Drew Adams [this message]

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=e0e5741c-a0cd-4931-a5ea-d02d8f02d298@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jacobgerlach@gmail.com \
    --cc=sergey.ivanes@gmail.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).