From: "Patricia J. Hawkins" <phawkins@connact.com>
To: "Paw Writer" <pawwriter@comcast.net>
Cc: EMACS Lists <gnu.emacs.help@gnu.org>
Subject: Re: Updating from Emacs 23.3.1 to 25.3
Date: Tue, 10 Oct 2017 11:38:19 -0400 [thread overview]
Message-ID: <87k203au8k.fsf@connact.com> (raw)
In-Reply-To: <000f01d3417c$366dec00$a349c400$@net> (Paw Writer's message of "Mon, 9 Oct 2017 23:59:45 -0400")
Congratulations, my combined emacs config files have 1644 lines of actual
not-commented-out code. (I should REALLY clean them up, but hey, they do work.)
They've been evolving since maybe 1990... I didn't think to capture my first set of
emacs config files which I started ~1986.
SO, when stuff breaks for whatever reason, here is what I do:
If the break is non-obvious, I just do divide-and-conquer to figure out what isn't
working in my .emacs or other setup files.
Comment out the bottom half of your .emacs (roughly; obviously you don't break code
to do this.) I generally comment it with something like ";;PJH;;" using "string
rectangle" so it's easy to strip out again.
Does that work? Yes? Great! Drop a comment line at the top of the commented section:
;;PJH works to here <2017-10-10 Tue>
Strip the comments from the top half of the commented section. Restart emacs.
Doesn't work? Great! The problem is in the chunk you just uncommented. Comment out
half of it. Restart emacs.
Lather, rinse, repeat.
Oh, and if you're not sure if a particular config file is getting read or not, go put
an obvious error in it. Or add a line that will do something clear and obvious. (I call
this, "If you can't fix it, break it worse.")
And as for directories moving around, below is a chunk from a historic .emacs file of
mine; note the commented-out code.
I had this thing shared with a Windows virtual machine, and running OK on both
the Ubuntu host and OSCAR, the Windows virtual machine, which had my elisp directory
mounted as z:
Oh, and then I did some fun stuff with guix, but IMO it's not ready for prime time
yet, so the directory structures from that are commented out too.
I do go for pragmatic over nice...
;; BEGIN .emacs CODE CHUNK
;;
;; (if (equal system-name "OSCAR")
;; (setq pjh-base-lispdir "z:/elisp"
;; pjh-emacs-base-lispdir "c:/emacs/emacs-23.1-bin-i386/emacs-23.1/"
;; custom-file "z:/.emacs-custom.el"
;; )
(setq pjh-base-lispdir (expand-file-name "~/elisp/")
pjh-emacs-base-lispdir "/usr/share/emacs/"
; pjh-emacs-base-lispdir "/home/pjh/.guix-profile/share/emacs"
custom-file "~/.emacs-custom.el")
;; )
;(if
; (not (equal (expand-file-name "~/elisp") (car load-path)))
(custom-set-variables
'(load-path
(append (list
pjh-base-lispdir
(concat pjh-base-lispdir "ljupdate")
; (concat pjh-base-lispdir "i3-emacs")
(concat pjh-base-lispdir "g-client")
(concat pjh-base-lispdir "site-lisp/w3m")
(concat pjh-base-lispdir "emacs-calfw-master")
;
; "/gnu/store/02ynsjc924vi2p36dxgz7r7q10wr2k41-profile/share/emacs/site-lisp/" ; what's in my personal guix installation
; "/home/pjh/.guix-profile/share/emacs/site-lisp" ; what's in the base emacs guix installation
; "/home/pjh/Downloads/guix-0.10.0/emacs/"
; (expand-file-name "/usr/share/emacs/site-lisp/")
; (expand-file-name "/usr/share/emacs/site-lisp/emacs-goodies-el/")
(concat pjh-base-lispdir "/home/pjh/.emacs.d/elpa") ;stuff installed from elpa
)
load-path
))
)
;(add-to-list 'load-path "/path/to/directory-with-guix.el")
;(with-eval-after-load 'guix-autoloads nil t)
;(require 'guix-autoloads nil t)
>>>>> "PW" == Paw Writer <pawwriter@comcast.net> writes:
PW> I am looking for some help with Upgrading Emacs. My current version is
PW> GNU Emacs 23.3.1. EMacs is now up to 25.3 and has a different
PW> directory structure. my .emacs has over 100 lines and doesn't run on
PW> 25.3 and I have one of my utilities which has been completely
PW> rewritten on 25.3 and won't run on 23.3.1.
PW> I have tried Googling updating Emacs and have not found any detailed
PW> help on what to do. Could someone give me some help?
PW> I just think I need someone here with me to walk me thru it. I already have
PW> 25.3 on my computer, in an Emacs1 directory, but the directory structure is
PW> so different, I have so much in my .emacs, and I need updated versions of
PW> many of the procedures and am not sure where to get them all. I live near
PW> Harrisburg, PA.
--
Patricia J. Hawkins
next prev parent reply other threads:[~2017-10-10 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 3:59 Updating from Emacs 23.3.1 to 25.3 Paw Writer
2017-10-10 12:38 ` Eli Zaretskii
2017-10-10 12:42 ` Kaushal Modi
2017-10-10 12:56 ` Benoît Coste
2017-10-10 15:38 ` Patricia J. Hawkins [this message]
2017-10-10 18:28 ` Paw Writer
[not found] <002701d3411c$7568d290$603a77b0$@net>
2017-10-10 2:39 ` Stefan Monnier
2017-10-10 4:00 ` Óscar Fuentes
2017-10-10 4:12 ` Stefan Monnier
2017-10-10 9:36 ` Phillip Lord
2017-10-10 12:32 ` Stefan Monnier
2017-10-10 14:20 ` Eli Zaretskii
2017-10-10 14:28 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k203au8k.fsf@connact.com \
--to=phawkins@connact.com \
--cc=gnu.emacs.help@gnu.org \
--cc=pawwriter@comcast.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.