From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs configuration
Date: Fri, 1 Oct 2021 23:34:45 +0300 [thread overview]
Message-ID: <YVdw5V1hFvfoWBou@protected.localdomain> (raw)
In-Reply-To: <877dexk920.fsf@zoho.eu>
* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-10-01 01:14]:
> Jean Louis wrote:
>
> > Not related to discussion, rather to "preprocessor", on my
> > side I am working with the database. And the database could
> > practically include certain Emacs Lisp expressions.
> > Those could evolve from multiple users. That is where
> > preprocessor could be useful on my side as to include such
> > customized snippets or modified functions for each user
> > being different. That is currently handled on my side by
> > using `eval'. Other possible use for preprocessor is to
> > dynamically include some date, signature, link snippets in
> > the script.
>
> But can't you do that with different functions and/or
> different arguments to the functions?
In the above example those can be different functions but they don't
come from file system, they may be different functions for different
users, coming from one or multiple databases, loaded shortly before
the moment of execution, not how it is common to load it longer time
before execution.
Specific example, main programmer does not need necessarily hard code
how an action will appear for the user. The action could be for
example to open PDF file at specific page. The type of PDF has Emacs
Lisp field value which can be customized by the user. Customization is
not on computer's file system, it is in the database.
> What's the one thing that makes the preprocessor indispensible?
In Emacs Lisp files, I don't use pre-processor. I use it rather in
Emacs Lisp snippets stored in the database, of shorter nature, and
text files that include Emacs Lisp. It is similar to Org mode that
expands specific blocks into something else what is otherwise written
in the file, like lists, tables, pictures.
Example is that people's and companies' contact information may
change, but the instruction is there for several people. If contact
information ever changes the instruction document will automatically
update itself because it is pre-processed. Instead of text "Contact
Emamnuel @ 123.COM" it could automatically update itself to "Contact
Emmanual @ xyz.com".
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2021-10-01 20:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 15:13 emacs configuration Jude DaShiell
2021-09-30 15:56 ` tomas
2021-09-30 16:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 15:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-30 17:32 ` 2QdxY4RzWzUUiLuE
2021-09-30 21:49 ` Jean Louis
2021-09-30 22:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-01 20:34 ` Jean Louis [this message]
2021-09-30 16:03 ` 2QdxY4RzWzUUiLuE
2021-09-30 16:38 ` John W Higgins
[not found] <mailman.1033485728.6848.help-gnu-emacs@gnu.org>
2002-10-01 20:45 ` Emacs configuration Jesper Harder
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 15:21 arthur.chereau
[not found] <mailman.1033477527.28155.help-gnu-emacs@gnu.org>
2002-10-01 14:09 ` Jesper Harder
2002-10-01 13:04 arthur.chereau
[not found] <mailman.1033377809.21117.help-gnu-emacs@gnu.org>
2002-09-30 17:01 ` Jesper Harder
2002-09-30 17:02 ` Kevin Rodgers
2002-10-01 6:04 ` Evgeny Roubinchtein
2002-10-01 14:57 ` Stefan Monnier <foo@acm.com>
2002-09-30 9:22 arthur.chereau
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=YVdw5V1hFvfoWBou@protected.localdomain \
--to=bugs@gnu.support \
--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).