From: Eduardo Ochs <eduardoochs@gmail.com>
To: Davin Pearson <davin.pearson@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Special Post: My own customisations to GNU Emacs
Date: Sat, 7 May 2022 22:02:24 -0300 [thread overview]
Message-ID: <CADs++6jN-Ka-1DF6WzRwP=qtLmLrkDtyMRoLO+wSquoHXQQXSw@mail.gmail.com> (raw)
In-Reply-To: <CAG9ihEtUuQ2GV+yqOJk=uXvYvfJ=CY0fV3mRPgnzfZ0FY8hepA@mail.gmail.com>
On Sat, 7 May 2022 at 20:04, Davin Pearson <davin.pearson@gmail.com> wrote:
> (...)
Hi Davin & all,
this seems to require Windows...
Here's what I did to unpack and inspect (VERY superficially) your code
- I'm posting it here because it may save other people a few minutes
of work:
• (eepitch-shell)
• (eepitch-kill)
• (eepitch-shell)
cd /tmp/
wget -nc http://davinpearson.nz/binaries/java-training-wheels--bagatelles_20220506-110613.tar.gz
rm -Rv /tmp/java-training-wheels/
tar -tvzf
/tmp/java-training-wheels--bagatelles_20220506-110613.tar.gz
tar -C /tmp/ -xvzf
/tmp/java-training-wheels--bagatelles_20220506-110613.tar.gz
cd /tmp/java-training-wheels/
# (find-file "/tmp/java-training-wheels/")
# (find-file "/tmp/java-training-wheels/dlisp/coolmacs/dmp-kill-ring--file.el")
# Some eev-isms:
# (code-c-d "jtw" "/tmp/java-training-wheels/")
# (find-jtwfile "")
# (find-jtwsh "find * | sort")
# (find-jtwgrep "grep --color=auto -nRH --null -e dmp-kill-ring *")
# (find-jtwfile "dlisp/coolmacs/dmp-kill-ring--file.el")
I have the impression that even on Windows your code will be
considered hard to test, and that you should try to make a minimal
version of it with less cruft. Do you know how to connect to the
#emacs IRC channel? You could try to discuss how to do that with the
people there...
Cheers,
Eduardo Ochs
http://angg.twu.net/#eev
next prev parent reply other threads:[~2022-05-08 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 23:03 Special Post: My own customisations to GNU Emacs Davin Pearson
2022-05-08 1:02 ` Eduardo Ochs [this message]
2022-05-17 23:23 ` Davin Pearson
2022-05-17 23:47 ` Eduardo Ochs
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='CADs++6jN-Ka-1DF6WzRwP=qtLmLrkDtyMRoLO+wSquoHXQQXSw@mail.gmail.com' \
--to=eduardoochs@gmail.com \
--cc=davin.pearson@gmail.com \
--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).