From: Uwe Brauer <oub@mat.ucm.es>
To: Robert Pluim <rpluim@gmail.com>
Cc: Uwe Brauer <oub@mat.ucm.es>, larsi@gnus.org, 45693@debbugs.gnu.org
Subject: bug#45693: [two word expansion works, but write-abbrev-file destroys it]
Date: Tue, 12 Jan 2021 09:01:30 +0100 [thread overview]
Message-ID: <87sg767fdx.fsf@mat.ucm.es> (raw)
In-Reply-To: <87v9cam56e.fsf@mat.ucm.es>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
> It should have been, and was in my testing
> Iʼve only tested my code, not proven it bug-free :-)
I think I found a bug. I restart my emacs with your patched abbrev file
and all my stuff, then I obtain the following error:
Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" ".abbrev_defs")
load(".abbrev_defs" nil t)
read-abbrev-file(".abbrev_defs" t)
quietly-read-abbrev-file(".abbrev_defs")
command-line()
normal-top-level()
This is part of the list of my files in the home directory
lrwxrwxrwx 1 oub oub 43 ene 11 21:14 .abbrev_defs -> /home/oub/ALLES/HGs/init_files/.abbrev_defs
-rw-r--r-- 1 oub oub 0 mar 12 2018 .abbrev_defs_xemacs
lrwxrwxrwx 1 oub oub 49 feb 6 2018 .abbrev-emacs_defs -> /home/oub/ALLES/HGs/init_files/.abbrev-emacs_defs
-rw-rw-r-- 1 oub oub 1,4K ene 11 20:57 abbrev-patch
-rw-rw-r-- 1 oub oub 1,4K nov 27 08:41 abstract2.patch
-rw------- 1 oub oub 1,4K nov 27 08:40 abstract.patch
So what works is
(read-abbrev-file "~/.abbrev_defs")
But not
(read-abbrev-file ".abbrev_defs")
what currently emacs is trying to do.
Uwe
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2021-01-12 8:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 15:54 bug#45693: 28.0.50; abbrev does not expand two words any more Uwe Brauer
2021-01-10 14:35 ` Lars Ingebrigtsen
2021-01-10 15:51 ` Uwe Brauer
2021-01-10 15:52 ` Lars Ingebrigtsen
2021-01-10 17:22 ` Uwe Brauer
2021-01-10 21:21 ` bug#45693: [two word expansion works, but write-abbrev-file destroys it] (was: bug#45693: 28.0.50; abbrev does not expand two words any more) Uwe Brauer
2021-01-11 10:49 ` bug#45693: [two word expansion works, but write-abbrev-file destroys it] Robert Pluim
2021-01-11 15:26 ` Eli Zaretskii
2021-01-11 15:50 ` Uwe Brauer
2021-01-11 17:38 ` Robert Pluim
2021-01-11 20:17 ` Uwe Brauer
2021-01-11 20:38 ` Robert Pluim
2021-01-11 20:48 ` Uwe Brauer
2021-01-11 21:03 ` Robert Pluim
2021-01-12 8:01 ` Uwe Brauer [this message]
2021-01-12 10:34 ` Robert Pluim
2021-01-12 13:26 ` Uwe Brauer
2021-01-12 16:45 ` Uwe Brauer
2021-01-12 17:59 ` Robert Pluim
2021-01-13 7:37 ` Uwe Brauer
2021-01-13 9:16 ` Robert Pluim
2021-01-13 9:28 ` Uwe Brauer
2021-01-13 9:39 ` Robert Pluim
2021-01-13 9:51 ` Uwe Brauer
2021-01-13 10:09 ` Robert Pluim
2021-01-13 13:18 ` Uwe Brauer
2021-01-13 14:03 ` Robert Pluim
2021-01-13 16:25 ` Uwe Brauer
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=87sg767fdx.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=45693@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).