From: Jean Louis <bugs@gnu.support>
To: Yuan Cao <yuancao85@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs in a Corporate Environment
Date: Wed, 12 Apr 2023 23:52:55 +0300 [thread overview]
Message-ID: <ZDcaJ6oEkJfVSCg3@protected.localdomain> (raw)
In-Reply-To: <CA+wx7tVo2xH39Z5zTQYiyU1FKyv+QyZrXb2Nsr=tjbcTCwLEcw@mail.gmail.com>
* Yuan Cao <yuancao85@gmail.com> [2023-04-12 22:50]:
> Hello,
>
> I was wondering if anyone here has experience getting Emacs accepted into
> the approved software list in a corporate environment and is willing to
> answer a few questions or point me in the right direction.
"approved software list" is heaven thanks decided by myself in my
corporate environment.
We are using Emacs as ERP daily, projected budgets, accounting,
project planning. So I am building RCD Notes for GNU Emacs is Dynamic
Knowledge Repository designed as envisioned by Doug Engelbart.
RCD Notes for GNU Emacs is Dynamic Knowledge Repository designed as
envisioned by Doug Engelbart. Backed up by PostgreSQL relational
database, RCD Notes provides features such as people management also
known as CRM or Customer Relationship Management, ERP or Enterprise
Resource Planning, WRS or Website Revision System and Hyperscope
Dynamic Knowledge Repository. It uses any kind of Emacs major modes
and any kind of lightweight markup languages for editing and writing
of any of elementary objects.
Emacs has a programming language built-in, and by using Stallman's
principles that "any kind of text is editable", then it applies to
editing relational databases. Great.
We manage many people, resources, finances and multiple projects
through Emacs as interface.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2023-04-12 20:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 19:48 Emacs in a Corporate Environment Yuan Cao
2023-04-12 20:10 ` Corwin Brust
2023-04-12 20:48 ` John Yates
2023-04-12 21:33 ` Yuan Cao
2023-04-13 0:08 ` Corwin Brust
2023-04-13 14:35 ` Marcin Borkowski
2023-04-14 14:36 ` Michael Albinus
2023-04-14 14:52 ` Eli Zaretskii
2023-04-14 15:08 ` Óscar Fuentes
2023-04-14 15:47 ` Eli Zaretskii
2023-04-14 16:11 ` tomas
2023-04-15 6:12 ` Marcin Borkowski
2023-04-15 7:31 ` tomas
2023-04-15 9:12 ` Marcin Borkowski
2023-04-15 6:11 ` Marcin Borkowski
2023-04-15 7:17 ` Eli Zaretskii
2023-04-15 7:34 ` tomas
2023-04-15 7:59 ` Eli Zaretskii
2023-04-15 8:21 ` tomas
2023-04-15 9:41 ` Eli Zaretskii
2023-04-15 11:16 ` Po Lu
2023-04-15 12:04 ` Marcin Borkowski
2023-04-15 12:18 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-04-15 13:22 ` tomas
2023-04-15 18:45 ` Michael Albinus
2023-04-15 6:10 ` Marcin Borkowski
2023-04-15 21:14 ` Björn Bidar
2023-04-16 7:51 ` Michael Albinus
2023-04-13 14:23 ` Marcin Borkowski
2023-04-13 17:23 ` Yuan Cao
2023-04-12 20:52 ` Jean Louis [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=ZDcaJ6oEkJfVSCg3@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=yuancao85@gmail.com \
/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).