From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Resources for an old newbie ?
Date: Mon, 22 May 2023 03:30:00 +0200 [thread overview]
Message-ID: <874jo56tlz.fsf@web.de> (raw)
In-Reply-To: CAJr-wt18w=zfhhj6hjg7SZYVfaT7zOUimSdY2pR+HOuD2Rh8qw@mail.gmail.com
Frederick Bartlett <frederick.bartlett@gmail.com> writes:
> E.g., I just tried to install helm and am completely baffled by the info
> and error messages I’m getting:
First I try to answer your specific questions:
> INFO: Loading /usr/share/emacs/site-lisp/site-start.d/lilypond-init.el
> (source)...
This looks like it belongs to something you installed in your OS: when
you install Emacs libraries with your OS package manager setup files go
to this site-lisp directory. Maybe ask your OS to which package this
file belongs, or ignore it for now.
> Since I invoked
> ./emacs/helm/emacs-helm.sh -P /usr/bin/emacs-28.2
> from my home directory, I would expect it to know where it is.
This emacs-helm.sh script is for testing and debugging Helm, it is not
for the end user!
Typically you install such packages from within the built-in emacs
package manager that you get when typing M-x list-packages RET. Then
you can (require 'helm) or call (helm-mode +1) in your init file (using
a "normally started" Emacs). Then see the documentation of the packages
for how to configure them.
Apart from these examples, the main question is: what do you want to do
and achieve in Emacs, is you basic understand of Lisp good enough to
allow you to edit your init file to get what you want (or do you need an
introduction? Emacs comes with an Info manual "Emacs Lisp Intro", we
can tell you how to read that from within Emacs. It teaches some basic
levels of (E)Lisp. Maybe that would be a good start).
After that the documentation that comes with Emacs plus this user list
should be enough to be able to go the following steps.
Michael.
next prev parent reply other threads:[~2023-05-22 1:30 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 0:44 Resources for an old newbie ? Frederick Bartlett
2023-05-22 0:50 ` Eduardo Ochs
2023-05-22 1:30 ` Michael Heerdegen [this message]
2023-05-22 1:39 ` Michael Heerdegen
2023-05-22 6:33 ` Basile Starynkevitch
2023-05-23 0:11 ` Michael Heerdegen
2023-05-23 5:31 ` Emanuel Berg
2023-05-23 20:19 ` Philip Kaludercic
2023-05-25 0:55 ` Emanuel Berg
2023-05-23 23:09 ` Michael Heerdegen
2023-05-25 1:13 ` Emanuel Berg
2023-05-26 3:28 ` Michael Heerdegen
2023-05-27 5:41 ` Emanuel Berg
2023-05-28 1:50 ` Michael Heerdegen
2023-05-28 21:23 ` Emanuel Berg
2023-05-24 4:25 ` tomas
2023-05-25 1:25 ` Emanuel Berg
2023-05-25 4:01 ` tomas
2023-05-26 1:26 ` David Masterson
2023-05-26 3:36 ` Michael Heerdegen
2023-05-26 4:13 ` Robby Zambito
2023-05-27 4:09 ` David Masterson
2023-05-27 5:29 ` Emanuel Berg
2023-05-29 22:13 ` David Masterson
2023-05-27 5:48 ` Emanuel Berg
2023-05-29 22:14 ` David Masterson
2023-05-27 17:48 ` Robby Zambito
2023-05-29 22:23 ` David Masterson
2023-05-28 2:12 ` Michael Heerdegen
2023-05-28 21:26 ` Emanuel Berg
2023-05-29 22:21 ` David Masterson
2023-05-29 22:52 ` Michael Heerdegen
2023-05-30 2:18 ` Emanuel Berg
2023-06-03 21:40 ` David Masterson
2023-05-30 23:24 ` Emanuel Berg
2023-05-31 3:12 ` Platon Pronko
2023-05-31 3:20 ` Emanuel Berg
2023-05-31 22:07 ` Michael Heerdegen
2023-06-03 21:45 ` David Masterson
2023-06-03 22:03 ` Michael Heerdegen
2023-06-03 22:39 ` David Masterson
2023-06-03 23:19 ` Michael Heerdegen
2023-06-04 1:00 ` David Masterson
2023-06-04 1:31 ` Emanuel Berg
2023-06-04 2:15 ` Michael Heerdegen
2023-06-04 5:23 ` David Masterson
2023-06-04 2:21 ` Emanuel Berg
2023-06-04 21:05 ` David Masterson
2023-06-06 16:45 ` Emanuel Berg
2023-06-04 3:02 ` Emanuel Berg
2023-06-04 21:01 ` David Masterson
2023-06-04 5:25 ` Eli Zaretskii
2023-06-04 7:08 ` Basile Starynkevitch
2023-06-04 20:35 ` David Masterson
2023-06-04 7:26 ` David Masterson
2023-06-04 7:37 ` Eli Zaretskii
2023-06-04 10:45 ` Emanuel Berg
2023-06-04 20:07 ` David Masterson
2023-06-04 22:12 ` Michael Heerdegen
2023-06-04 22:36 ` David Masterson
2023-06-05 20:34 ` Emanuel Berg
2023-06-05 20:35 ` Emanuel Berg
2023-06-04 10:39 ` Emanuel Berg
2023-06-04 20:23 ` David Masterson
2023-06-05 0:29 ` Michael Heerdegen
2023-06-05 2:22 ` David Masterson
2023-06-05 2:59 ` Michael Heerdegen
2023-06-06 1:19 ` Emanuel Berg
2023-06-06 16:35 ` Emanuel Berg
2023-06-11 3:14 ` Michael Heerdegen
2023-06-11 4:48 ` David Masterson
2023-06-11 6:02 ` Emanuel Berg
2023-06-11 23:33 ` Michael Heerdegen
2023-06-11 23:41 ` Emanuel Berg
2023-06-16 2:22 ` Michael Heerdegen
2023-06-16 2:27 ` Michael Heerdegen
2023-06-11 5:54 ` Emanuel Berg
2023-06-11 23:42 ` Michael Heerdegen
2023-06-11 23:56 ` Emanuel Berg
2023-06-05 20:41 ` Emanuel Berg
2023-06-03 21:33 ` David Masterson
2023-05-26 4:28 ` tomas
2023-05-26 11:34 ` Robert Pluim
2023-05-26 12:06 ` tomas
2023-05-26 14:11 ` Robert Pluim
2023-05-26 21:40 ` Emanuel Berg
2023-06-08 8:39 ` 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=874jo56tlz.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).