From: Ship Mints <shipmints@gmail.com>
To: 72298@debbugs.gnu.org
Subject: bug#72298: Should python-mode-abbrev-table declare :parents python-base-mode-abbrev-table?
Date: Sat, 17 Aug 2024 09:53:15 -0400 [thread overview]
Message-ID: <CAN+1HbrJKpssuvqwFXCcV7eYmPSswsMeWZPs-HysduM4qJAsRg@mail.gmail.com> (raw)
In-Reply-To: <CAN+1HbobFYLqzKLAB=HNC5rZERButUcLBnzMaSU3r_gQXi+vsQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
Greetings. Curious if I'm barking up the wrong tree with this assessment...
On Thu, Jul 25, 2024 at 2:33 PM Ship Mints <shipmints@gmail.com> wrote:
> An example of a personal hack to make this work could be to add something
> like this to a python-mode-hook:
>
> (if (derived-mode-p 'python-base-mode)
> (setq local-abbrev-table python-base-mode-abbrev-table))
>
> On Thu, Jul 25, 2024 at 2:15 PM Ship Mints <shipmints@gmail.com> wrote:
>
>> I was expecting that python-base-mode-abbrev-table would apply to both
>> python-mode and python-ts-mode buffers. python-ts-mode doesn't derive from
>> python-mode so the abbrev tables aren't shared by default. Unless I'm
>> missing something, using a base table doesn't work for me.
>>
>> (define-abbrev-table 'python-mode-abbrev-table ()
>> "Abbrev table for Python mode."
>> ;; should this:
>> :parents (list python-mode-skeleton-abbrev-table))
>> ;; be defined thusly?
>> :parents (list python-base-mode-abbrev-table
>> python-mode-skeleton-abbrev-table))
>>
>> I tried to find guidance on this outside of hacking abbrev tables
>> manually to be shared. Perhaps other people have the same expectation.
>>
>> Thank you,
>>
>> Stephane
>>
>
[-- Attachment #2: Type: text/html, Size: 2803 bytes --]
next prev parent reply other threads:[~2024-08-17 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 18:13 bug#72298: Should python-mode-abbrev-table declare :parents python-base-mode-abbrev-table? Ship Mints
2024-07-25 18:33 ` Ship Mints
2024-08-17 13:53 ` Ship Mints [this message]
2024-08-24 8:45 ` Eli Zaretskii
2024-08-24 11:29 ` kobarity
2024-08-24 14:14 ` Ship Mints
2024-08-25 0:34 ` kobarity
2024-08-31 9:43 ` Eli Zaretskii
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=CAN+1HbrJKpssuvqwFXCcV7eYmPSswsMeWZPs-HysduM4qJAsRg@mail.gmail.com \
--to=shipmints@gmail.com \
--cc=72298@debbugs.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.
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).