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, monnier@iro.umontreal.ca
Subject: Re: New Package: sticky-shell
Date: Sun, 19 Feb 2023 15:56:49 -0500	[thread overview]
Message-ID: <CAP5CrM2q6oVRAHEA3f0xaEvP+BU55aCROFEh8xwRK99n080nwA@mail.gmail.com> (raw)
In-Reply-To: <Y675pGjpLyhZuL3p@protected.localdomain>

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

Just wanted to let anyone interested in this package know: I've added it to
MELPA. It can be installed as "sticky-shell".
I've also improved its support of terminal modes and shell modes. You can
find more info at the repo <https://github.com/andyjda/sticky-shell>

On Fri, Dec 30, 2022 at 9:58 AM Jean Louis <bugs@gnu.support> wrote:

> * Andrew De Angelis <bobodeangelis@gmail.com> [2022-12-28 18:35]:
> > @Jean Louis
> > Thank you. I still can't reproduce the error, but I understand its
> causes.
> > Line 72:
> > `(aset prompt (- (length prompt) 1) 0) ; remove the newline ending char`
> > was intended to remove the newline char that showed up in my header as
> > '^J'. There must be something different in your configuration that
> already
> > removes it from the header/prompt, so deleting it again caused the issue.
> > I've replaced this line with the more explicit:
> > `(string-trim-right prompt "[ \t\n\r]+"))) ; remove the newline ending
> char`
> > Please try out the latest code <https://github.com/andyjda/sticky-shell
> >and
> > let me know your experience.
>
> Thank you.  I do not see that problem anymore, though I tested it for
> only short time.
>
> Here are matches for `shell''of my custom.el if you wish to test if
> that fiddles with your package.
>
> 7 matches for "shell" in buffer: custom.el
>      78: '(async-shell-command-buffer 'new-buffer)
>     524: '(shell-command-prompt-show-cwd t)
>     525: '(shell-completion-execonly nil)
>
>
> --
> 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: 2443 bytes --]

      reply	other threads:[~2023-02-19 20:56 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
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 [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=CAP5CrM2q6oVRAHEA3f0xaEvP+BU55aCROFEh8xwRK99n080nwA@mail.gmail.com \
    --to=bobodeangelis@gmail.com \
    --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).