From: Drew Adams <drew.adams@oracle.com>
To: Yuri Khan <yuri.v.khan@gmail.com>, Christopher Dimech <dimech@gmx.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
Jamie Beardslee <jdb@jamzattack.xyz>
Subject: RE: Scratch buffer on either side of current buffer
Date: Sat, 21 Nov 2020 11:50:51 -0800 (PST) [thread overview]
Message-ID: <fbe979bc-b65b-4c2b-8507-f44e1528f27b@default> (raw)
In-Reply-To: <CAP_d_8VNWfm-x1MdPi=U0aqSTX=BmLFYy0BxEyHZyY6CEOA5uw@mail.gmail.com>
> > Astonishing!
>
> My point is that you should ask for the thing you need or want, not
> for the approach that first comes into your head. Inferring the want
> from the ask is not always easy.
Yup. That makes things easier for the questioner,
and easier for answerers.
https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem
And because it avoids wasted energy it often means
that you get more or better help in the future.
Just like the frustration of a moving goal post
(the ever-evolving/moving question), going X-Y
can lead to people giving up on helping the X-Yer.
prev parent reply other threads:[~2020-11-21 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 1:41 Scratch buffer on either side of current buffer Christopher Dimech
2020-11-21 5:02 ` Jamie Beardslee
2020-11-21 14:09 ` Christopher Dimech
2020-11-21 14:52 ` Yuri Khan
2020-11-21 15:43 ` Christopher Dimech
2020-11-21 16:03 ` Yuri Khan
2020-11-21 16:12 ` Christopher Dimech
2020-11-21 16:43 ` Christopher Dimech
2020-11-21 19:50 ` 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=fbe979bc-b65b-4c2b-8507-f44e1528f27b@default \
--to=drew.adams@oracle.com \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jdb@jamzattack.xyz \
--cc=yuri.v.khan@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).