From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: Re: where to put files
Date: Tue, 26 Mar 2019 03:48:17 +0100 [thread overview]
Message-ID: <865zs6xsem.fsf@zoho.eu> (raw)
In-Reply-To: 87k1gmxxpm.fsf@ra.horus-it.com
Ralph Seichter wrote:
>> If it isn't a secret, what does it tell
>> *you*?
>
> It tells me that what I learned over the last
> 30+ years is still valid today: When posting
> in a mailing list, never expect applause,
> feedback or gratitude.
Oh, no! I've been doing that for 10+ years!
Well, not really. I never expected applause,
neither gratitude - well, gratitude perhaps in
the sense "you are creative with the software,
that's good, keep it up", but not gratitude in
the sense "thanks for a bunch of great code,
I'll start using it immediately myself!".
Besides, I think my computer personality
doesn't lend itself to that, either (at least
not 2019, perhaps never).
And I never thought my stuff was brilliant -
creative perhaps, but not anything out of the
ordinary in terms of the technology itself.
But *feedback*? Why shouldn't one expect that
on a mailing list/newsgroup about a particular
piece of software, when the posts are exactly
about that?
> The best you can hope for is not to annoy too
> many people, unless that's your
> intended purpose.
Obviously you are right but I don't understand
it one byte or even bit. If 20 or so guys
posted code here every second day or so,
I would be *delighted* (and offer feedback
wherever I could, even applause and gratitude
for that matter if I liked their stuff that
much I'd use it myself).
> Git is available as a command line client,
> various graphical clients, and via web UIs.
> Find a sympathetic person with an
> Internet-capable computer and spend some time
> reading:
>
> https://git-scm.com
> https://gitlab.com
? I have internet - I'm speaking to you right
now! But if by "Internet-capable computer" you
mean JavaScript etc and a monitor with some
computer bum beside me on a couch watching some
nerdy US TV show I'm sorry, never - if it can't
be done all-Emacs-w3m or all-CLI (including the
documentation) I have to recycle a new
computer before I can do it...
But thanks anyway, God willing it will happen.
I have bookmarked those links :)
> Have fun studying the documentation. ;-)
If you think documentation will help you read
it. You better at it.
:)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2019-03-26 2:48 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 5:12 todo-did.el complete rewrite Emanuel Berg
2019-03-25 6:57 ` Van L
2019-03-25 18:25 ` license and where to safely store all code (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-25 18:50 ` [OFF TOPIC] " Emanuel Berg
2019-03-25 20:04 ` todo-did.el complete rewrite Ralph Seichter
2019-03-26 0:07 ` where to put files (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-26 0:53 ` where to put files Ralph Seichter
2019-03-26 2:48 ` Emanuel Berg [this message]
2019-03-26 17:15 ` Robert Thorpe
2019-03-26 8:36 ` Van L
2019-03-25 20:45 ` todo-did.el complete rewrite Stefan Monnier
2019-03-25 23:41 ` Emanuel Berg
2019-03-26 17:35 ` Stefan Monnier
2019-03-27 0:37 ` Emanuel Berg
2019-03-27 1:42 ` Amin Bandali
2019-03-27 13:12 ` what I should do, and the "Emacs News Ezine" (was: Re: todo-did.el complete rewrite) Emanuel Berg
2019-03-27 13:40 ` what I should do, and the "Emacs News Ezine" Michael Albinus
2019-03-29 9:16 ` Marcin Borkowski
2019-03-29 12:49 ` Óscar Fuentes
2019-04-01 22:07 ` Emanuel Berg
2019-03-27 14:40 ` Amin Bandali
2019-03-28 0:05 ` Van L
2019-03-29 1:38 ` Amin Bandali
2019-03-29 6:27 ` Emanuel Berg
2019-04-27 14:58 ` Van L
2019-04-27 21:09 ` Emanuel Berg
2019-03-29 5:27 ` Sacha Chua
2019-03-29 14:44 ` Drew Adams
2019-04-01 22:11 ` Emanuel Berg
2019-04-26 7:04 ` Van L
2019-04-26 7:39 ` Emanuel Berg
2019-04-27 13:07 ` Van L
2019-04-27 21:07 ` Emanuel Berg
2019-04-26 7:47 ` tomas
2019-04-27 21:10 ` Emanuel Berg
2019-04-29 3:32 ` Van L
2019-04-04 4:18 ` Xavier Maillard
2019-04-04 3:31 ` Emanuel Berg
2019-04-17 0:39 ` Sacha Chua
2019-04-17 1:53 ` Emanuel Berg
2019-04-17 11:02 ` Van L
2019-04-17 19:07 ` Emanuel Berg
2019-04-01 13:07 ` Emanuel Berg
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=865zs6xsem.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--cc=help-gnu-emacs@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.
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).