From: Christopher Dimech <dimech@gmx.com>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org, lisa-asket@perso.be
Subject: Beauty of Emacs Lisp
Date: Sat, 10 Jul 2021 08:17:23 +0200 [thread overview]
Message-ID: <trinity-358db6e5-f010-41a7-917d-c00cc362ebcc-1625897843373@3c-app-mailcom-bs16> (raw)
In-Reply-To: <YOk1p6qZB+GZB6P9@protected.localdomain>
One thing to work on is outline-minor-mode as it has not been fully completed.
There are a couple of things
1. Get Outline Levels to use a different colour according to level.
2. There does not seem to be a default setup for sh-mode.
3. Separate code headings from user defined headings
Task 3 would help users collect a number of defuns or region into a
heading or subheading, so that the code could be better organsised.
Perhaps the only thing a lisp expression starting with `(` un the first
column would be to to only have show-entry and hide-entry.
Felicitations
Christopher
> Sent: Saturday, July 10, 2021 at 5:52 PM
> From: "Jean Louis" <bugs@gnu.support>
> To: lisa-asket@perso.be, help-gnu-emacs@gnu.org
> Subject: Beauty of Emacs Lisp
>
> Beautiful programming language Emacs Lisp is very helpful and
> assistive to human, integrated with editor and graphical user
> interface that easy the tasks for computer user. Emacs Lisp can even
> handle it's own and your own development workflow - as it has it's own
> IDE.
>
> To make your application well integrated, I highly recommend Emacs
> Lisp in all its glory. By learning Emacs Lisp, we can make a more
> complete project with less time to setup & maintain. In addition to
> Emacs Lisp, you also can use Emacs as a tool to solve problems that
> may never be solved using any other programming environment.
>
> We also are always working towards making a better user experience for
> the program user. The only problem we have with it is that there are
> some big and unexpected challenges that need to be worked out to
> optimize the performance.
>
> Please don't hesitate to ask us to help you for your project. The goal
> is not to solve some major technical challenges. You simply have to
> find ways to solve this problem in Emacs Lisp and help it improve in
> general. As of now, if you have any need for advanced code on Emacs
> Lisp in future releases, we recommend you to ask us to help you as
> well. We are confident we can solve your problems with our own help.
>
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> In support of Richard M. Stallman
> https://stallmansupport.org/
>
> P.S. There is truth inside, the above has been to 98% generated by AI.
>
>
next prev parent reply other threads:[~2021-07-10 6:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 11:55 Menu functionality lisa-asket
2021-07-09 12:14 ` tomas
2021-07-09 23:25 ` lisa-asket
2021-07-10 2:47 ` Jean Louis
2021-07-10 3:09 ` lisa-asket
2021-07-10 3:48 ` lisa-asket
2021-07-10 4:07 ` lisa-asket
2021-07-10 4:14 ` Jean Louis
2021-07-10 4:36 ` lisa-asket
2021-07-10 4:39 ` lisa-asket
2021-07-10 4:56 ` Jean Louis
2021-07-10 5:06 ` lisa-asket
2021-07-10 5:41 ` Jean Louis
2021-07-10 5:52 ` Beauty of Emacs Lisp Jean Louis
2021-07-10 6:17 ` Christopher Dimech [this message]
2021-07-10 5:59 ` Menu functionality lisa-asket
2021-07-10 17:44 ` Jean Louis
2021-07-10 19:21 ` lisa-asket
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-358db6e5-f010-41a7-917d-c00cc362ebcc-1625897843373@3c-app-mailcom-bs16 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=lisa-asket@perso.be \
/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).