From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: Define interactive function with arguments
Date: Fri, 9 Oct 2020 16:24:58 +0200 [thread overview]
Message-ID: <trinity-e9421a68-e9b4-4888-a7a9-8964e38e596d-1602253498757@3c-app-mailcom-bs09> (raw)
In-Reply-To: <877drzqz06.fsf@ebih.ebihd>
Have looked at what I send and have used indentation, whitespace,
etc but during the sending operation it is scrambling the whole code.
Will look into it so it will show right.
> Sent: Friday, October 09, 2020 at 4:01 PM
> 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: Define interactive function with arguments
>
> Christopher Dimech wrote:
>
> > Your comment simply means, look at the manual [...]
>
> If you don't want to look at the manual, how about:
>
> 1. think
>
> 2. byte compile and read the warnings and errors
>
> 3. do C-h f FUN RET and C-h v VAR RET for
> everything in your ... code
>
> 4. OK?
>
> And yes, TBH do us all a favor and drop that style :$
> use proper whitespace, case, names that makes sense,
> indentation, comments, and all that, before this
> turns into an embarrassment to the sport :(
>
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>
prev parent reply other threads:[~2020-10-09 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 23:15 Define interactive function with arguments Christopher Dimech
2020-10-08 23:41 ` Stefan Monnier
2020-10-08 23:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-09 6:38 ` Christopher Dimech
2020-10-09 7:18 ` Joost Kremers
2020-10-09 8:57 ` Christopher Dimech
2020-10-09 9:22 ` Joost Kremers
2020-10-09 9:52 ` Christopher Dimech
2020-10-09 14:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-09 14:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-09 14:24 ` Christopher Dimech [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=trinity-e9421a68-e9b4-4888-a7a9-8964e38e596d-1602253498757@3c-app-mailcom-bs09 \
--to=dimech@gmx.com \
--cc=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).