unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: uzibalqa <uzibalqa@proton.me>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Abbrev for shorthand purposes
Date: Thu, 11 Aug 2022 06:43:14 +0300	[thread overview]
Message-ID: <YvR60tN7mR6L70ru@protected.localdomain> (raw)
In-Reply-To: <j1wHUoLEqo0KB2Ctm_6C9-AO_afwQ8ORtMw8qjw1dgHCnecpM1aLShq6TfLHnRvM-roPwe0U0kGYvwxG2zjyVImHk8k4WnoCC7aNRCECP2M=@proton.me>

* uzibalqa <uzibalqa@proton.me> [2022-08-11 00:43]:
> > Purpose of abbrevs was not to use them programmatically, but to have
> > it handy to quickly add them while writing text.
> 
> I am using them programmatically because I want to implement a specific
> scheme for short writing.

You can implement it rather by thinking and using Emacs built-in
functions. You are inserting them into parenthesis, but you can insert them into
parenthesises by using built in Emacs functions as well, without
worries.

Your file will be saved. You may reuse the information.

> Yes I can complete the word "sentimental", but am struggling on how the word can then be
> changed to  "s--l".

For that you do following: 

- write s--l

- put cursor after s--l

- Press C-2 C-x a g

  This is because C-2 or C-u 2 is equivalent of going 2 words back, as
  s--l probably looks as 2 words to Emacs because of dashes.

- insert "sentimental"

- when you write sentimental it will expand into s--l

That method is faster.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  reply	other threads:[~2022-08-11  3:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  5:31 Abbrev for shorthand purposes uzibalqa via Users list for the GNU Emacs text editor
2022-08-07  0:08 ` kf
2022-08-10 20:30 ` Jean Louis
2022-08-10 21:43   ` uzibalqa
2022-08-11  3:43     ` Jean Louis [this message]
2022-08-11 12:28       ` uzibalqa

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=YvR60tN7mR6L70ru@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=uzibalqa@proton.me \
    /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).