unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: <miha@kamnitnik.top>
Cc: emacs-devel@gnu.org
Subject: Re: ELPA: new package capf-autosuggest
Date: Thu, 21 Oct 2021 18:24:44 +0000	[thread overview]
Message-ID: <87mtn2tevn.fsf@posteo.net> (raw)
In-Reply-To: <87a6j2b5z9.fsf@miha-pc> (miha@kamnitnik.top's message of "Thu, 21 Oct 2021 20:14:18 +0200")

<miha@kamnitnik.top> writes:

> Philip Kaludercic <philip.kaludercic@fau.de> writes:
>
>> <miha@kamnitnik.top> writes:
>>
>>> Thanks, now done.
>>
>> Great, it builds now.
>>
>> Looking at the file, there seem to be a few checkdoc issues that could
>> be easily fixed. I guess that would be nice to see. Along these lines it
>> might also be cool to mark the Commentary sections "Instillation" (that
>> could be updated when the package is added), "Configuration", ... as
>> subsections of Commentary by having them begin with four
>> semicolons. That way when using outline-minor-mode, you'll see all of
>> them when the section is folded.
>
> Thanks for suggestions, now done.

1+

>> A general question I have is if this could be generalized to a general
>> completion system? You of course don't have to, I'm asking more out of
>> personal curiosity.
>
> It already is, enabling 'capf-autosuggest-mode' in an ordinary buffer
> displays an auto-suggestion for the first completion at point candidate
> as you type. By default, it is only displayed if point is at EOL.
> However, I don't advertise this feature that much mostly because I find
> it a bit intrusive. For more information, including how to lift the EOL
> restriction, you can read the ";;;; Details" section.

Yes, I saw that and wanted to know if you were planning to extend
capf-autosuggest in this direction or not. It seems interesting (and I
remember CEDET had something like this), but it isn't easy to get right,
I agree.

>> Otherwise, I can add it the package to ELPA with autosync'ing, unless
>> there are any objections.
>
> Okay, thanks.

I'll wait for a day or so, just to wait for responses.

-- 
	Philip Kaludercic



      reply	other threads:[~2021-10-21 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 21:30 ELPA: new package capf-autosuggest miha
2021-10-21 13:43 ` Philip Kaludercic
2021-10-21 14:10   ` miha
2021-10-21 14:55     ` Philip Kaludercic
2021-10-21 16:01       ` miha
2021-10-21 17:17         ` philipk
2021-10-21 17:18         ` Philip Kaludercic
2021-10-21 18:14           ` miha
2021-10-21 18:24             ` Philip Kaludercic [this message]

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=87mtn2tevn.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=miha@kamnitnik.top \
    /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).