From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How to rename files to numbers in Eshell?
Date: Fri, 01 Oct 2021 23:34:49 +0200 [thread overview]
Message-ID: <875yugh1ja.fsf@zoho.eu> (raw)
In-Reply-To: YVd00ZlU74TWOKoo@protected.localdomain
Jean Louis wrote:
> Just that for my needs speed does not matter much.
> What really matters is the integration opportunity that
> Emacs offers. We don't have our computing so prepared to be
> fully integrated, but we have got opportunities to make
> it so.
I agree that's super important but I thought that was possible
with SLIME. Maybe it is theoretically, maybe it is in practice
as well only I didn't crack the code ... but no, never came
close to the Elisp interactive feel.
> We don't have file sharing well integrated in Emacs.
> For example there is no quick Dired function to email a file
> or set of files.
Easy enough to fix - see source last - but I don't know why it
isn't there to begin with. either political reasons or no one
did it.
> Back to Common Lisp. It is even less integrated for basic
> needs. In Emacs I can mark files and share them to other
> device or use functions to share them by email or publish
> files on remote devices. In Common Lisp I have to program
> everything myself, too much of it. Marking of files I would
> need to program myself. Taking care of even lower
> level functions.
It is like that, is it? Or did you overlook some key packages
in that field perhaps? I don't think so necessarily but it is
possible ...
> Everything can be done with Common Lisp and Scheme, but it
> is more work with Common Lisp as compared to Emacs once user
> understands how much of it is already close to fingertips.
How much Elisp is there around compared to all CL and all
Scheme and all other Lisp diagrams? Pie chart!
>> To translate either Perl or Python to Elisp to I would
>> _never_ do ...
>
> I have done that from Perl to Common Lisp, from Perl to
> Emacs Lisp.
Yeah, this whole translating stuff is foreign to me ... even
if I did it I would call it a re-implementation or second
attempt rather than a "translation"
> There is fundamental principle that almost anything we do on
> computer is related to writing, thus editing. In your
> example you are mentioning it without notice, you have to
> edit and type text in xterm and within tmux.
Well, I know I type what I think is "a lot" but what the Jonas
Svensson of Sweden does and does not with his computer, i have
no clue. so while I don't think he "edits" all day and night
long, rather he uses the computers with GUIs only.
;;; -*- lexical-binding: t -*-
;;;
;;; this file:
;;; http://user.it.uu.se/~embe8573/emacs-init/gnus/mail-to-many.el
;;; https://dataswamp.org/~incal/emacs-init/gnus/mail-to-many.el
(require 'gnus-msg)
(require 'message)
(defun send-mail-to-many (to-list subject body)
(dolist (to to-list)
(send-mail-to to subject body) ))
(defun send-mail-to (to subject body)
(gnus-post-news 'post "")
(message-goto-to) (insert to)
(message-goto-subject) (insert subject)
(message-goto-body) (insert body)
(message-send-and-exit) )
(provide 'mail-to-many)
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-10-01 21:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 13:15 How to rename files to numbers in Eshell? Felix E. Klee
2021-09-11 13:40 ` Jean Louis
2021-09-12 8:44 ` Felix E. Klee
2021-09-12 19:03 ` Jean Louis
2021-09-13 9:28 ` Jean Louis
2021-09-13 11:52 ` tomas
2021-09-14 7:42 ` Felix E. Klee
2021-09-14 9:17 ` Jean Louis
2021-09-14 9:32 ` tomas
2021-09-14 11:11 ` Felix E. Klee
2021-09-14 13:37 ` Jean Louis
2021-09-14 15:48 ` Felix E. Klee
2021-09-16 22:37 ` Michael Heerdegen
2021-09-16 22:47 ` Michael Heerdegen
2021-09-17 7:27 ` Felix E. Klee
2021-09-24 7:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-25 13:43 ` Jean Louis
2021-09-26 2:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 6:38 ` Felix E. Klee
2021-09-30 7:37 ` Jean Louis
2021-09-30 7:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 13:17 ` Felix E. Klee
2021-09-30 15:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 21:42 ` Jean Louis
2021-10-01 0:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-01 20:51 ` Jean Louis
2021-10-01 21:34 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-10-02 7:53 ` Lack of integration in Emacs - it was " Jean Louis
2021-10-03 8:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-03 9:27 ` Jean Louis
2021-10-04 3:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-04 10:15 ` Jean Louis
2021-10-04 11:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-22 14:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-22 14:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-16 12:15 ` Felix E. Klee
2021-09-16 15:11 ` Nick Dokos
2021-09-16 16:07 ` Felix E. Klee
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=875yugh1ja.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).