unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew De Angelis <bobodeangelis@gmail.com>
To: Andrew De Angelis <bobodeangelis@gmail.com>,
	emacs-devel@gnu.org, bugs@gnu.support, monnier@iro.umontreal.ca
Subject: Re: New Package: sticky-shell
Date: Wed, 14 Dec 2022 00:23:56 -0500	[thread overview]
Message-ID: <CAP5CrM2m91apdnrAr8ctO91G1z0knJv1YoGSb+Ab3S+O7-xc-A@mail.gmail.com> (raw)
In-Reply-To: <Y5jDR6ma6igncp1i@protected.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]

@Stefan Monnier

> Step 1 (same as for GNU ELPA): get the copyright paperwork in order.
>        I don't see your name in the FSF's copyright assigners list, so
>        either it's still in process or you haven't started yet.
>        Let me know if you need help with that.

I have not started this. This would be my first contribution to free
software, so I'm not very familiar with the process. Would greatly
appreciate it if you could give me a rundown of what to do or just point me
to the right documentation.

About `sticky-shell-prompt-modifiers`, I welcome any feedback on this
current approach. My idea was to try to make it simpler for the end user,
since:

(add-to-list 'sticky-shell-prompt-modifiers '(propertize 'face
'minibuffer-prompt))

would be less verbose then:
(advice-add 'sticky-shell-modified-prompt :filter-return (lambda (arg)
(propertize arg 'face 'minibuffer-prompt)))

Even though they accomplish the same thing. But I'm having second thoughts,
as I see how the latter is probably more familiar to Emas users.
And I'm also worried about the issue of the macro getting expanded every
time we refresh the header line: I was thinking a possible solution would
be to create a different macro that defines the function
`sticky-shell-modified-prompt', using the user's custom modifying
functions, only once when the mode is activated.

Honestly, especially if we 're planning on including this as part of
`shell.el`, I think the way to go might just be to remove the
`sticky-shell-prompt-modifiers` mechanism. If users want to propertize the
header or customize it in any way, they can use the `advice-add` function
they should already be somewhat used to.

@Jean Louis
I'm sorry but I am unable to reproduce your issue. Is anyone else
experiencing problems with sticky-shell?

On Tue, Dec 13, 2022 at 2:20 PM Jean Louis <bugs@gnu.support> wrote:

> * Andrew De Angelis <bobodeangelis@gmail.com> [2022-12-13 14:48]:
> > @Jean Louis, about
> >
> > > I have tested it, it does not work reliably.
> > >
> > Thanks for flagging this. What version of Emacs are you running, and do
> you
> > have any special shell configuration?
> > I built Emacs from master last week, did "emacs -q" and sticky-shell
> works
> > as expected.
>
> I use development version, it did not work well, I have explained what.
>
>
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> In support of Richard M. Stallman
> https://stallmansupport.org/
>

[-- Attachment #2: Type: text/html, Size: 3691 bytes --]

  reply	other threads:[~2022-12-14  5:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  0:05 New Package: sticky-shell Andrew De Angelis
2022-12-12 18:33 ` Philip Kaludercic
2022-12-12 18:45 ` Stefan Monnier
2022-12-12 18:55   ` Akib Azmain Turja
2022-12-13  3:27 ` Jean Louis
2022-12-13  4:07   ` Andrew De Angelis
2022-12-13 14:22     ` Stefan Monnier
2022-12-13 18:24     ` Jean Louis
2022-12-14  5:23       ` Andrew De Angelis [this message]
2022-12-14 13:41         ` Stefan Monnier
2022-12-16 10:20         ` Jean Louis
2022-12-28 15:34           ` Andrew De Angelis
2022-12-30 14:45             ` Jean Louis
2023-02-19 20:56               ` Andrew De Angelis

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=CAP5CrM2m91apdnrAr8ctO91G1z0knJv1YoGSb+Ab3S+O7-xc-A@mail.gmail.com \
    --to=bobodeangelis@gmail.com \
    --cc=bugs@gnu.support \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).