From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: ~Make emacs friendlier: package documentation [POC CODE INCLUDED]
Date: Sun, 18 Oct 2020 12:29:17 -0400 [thread overview]
Message-ID: <20201018162917.xlh3bpxrrfuqw43b@E15-2016.optimum.net> (raw)
In-Reply-To: <83r1pvr0av.fsf@gnu.org>
On 2020-10-18 19:00, Eli Zaretskii wrote:
> > Date: Sun, 18 Oct 2020 11:28:30 -0400
> > From: Boruch Baum <boruch_baum@gmx.com>
> > Cc: emacs-devel@gnu.org
> >
> > > Well, would you like then to modify your code along these lines, and
> > > submit a modified patch? TIA.
> >
> > At this point, not at all, because no one seems to have made even the
> > slightest effort to evaluate the current submission and provide real
> > feedback. I get the feeling that I'm being asked to invest time and
> > effort only to have it all ignored.
>
> It will not be ignored, because it adds useful features.
You couldn't possibly have an informed opinion about that because you
haven't tried it yourself.
> It's just the that the current form is so different from the final one
> in many aspects
"many aspects"? The integration that you proposed is just adding a link.
> that having to review it now would mean we have to review it twice,
> which I at least would like to avoid.
grumble.
> So please don't feel discouraged.
Not helpful.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2020-10-18 16:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 19:09 ~Make emacs friendlier: package documentation [POC CODE INCLUDED] Boruch Baum
2020-10-15 19:24 ` Eli Zaretskii
2020-10-15 19:41 ` Boruch Baum
2020-10-16 6:39 ` Eli Zaretskii
2020-10-16 7:34 ` Boruch Baum
2020-10-16 10:20 ` Eli Zaretskii
2020-10-18 5:58 ` Boruch Baum
2020-10-18 14:53 ` Eli Zaretskii
2020-10-18 15:05 ` Boruch Baum
2020-10-18 15:12 ` Eli Zaretskii
2020-10-18 15:28 ` Boruch Baum
2020-10-18 16:00 ` Eli Zaretskii
2020-10-18 16:29 ` Boruch Baum [this message]
2020-10-18 17:05 ` Eli Zaretskii
2020-10-18 13:11 ` Stefan Monnier
2020-10-18 14:43 ` Boruch Baum
2020-10-18 15:50 ` Stefan Kangas
2020-10-18 16:20 ` Boruch Baum
2020-10-18 17:13 ` Stefan Kangas
2020-10-18 20:40 ` Kévin Le Gouguec
2020-10-19 2:55 ` Boruch Baum
2020-10-21 5:52 ` Kévin Le Gouguec
2020-10-21 6:00 ` Boruch Baum
2020-10-21 22:31 ` Stefan Monnier
2020-10-18 15:58 ` Boruch Baum
2020-10-18 20:18 ` Stefan Monnier
2020-10-19 2:24 ` Eli Zaretskii
2020-10-19 2:59 ` Boruch Baum
2020-10-19 3:16 ` Stefan Monnier
2020-10-20 5:11 ` Richard Stallman
2020-10-20 5:51 ` Boruch Baum
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=20201018162917.xlh3bpxrrfuqw43b@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).