all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [PATCH pmg-api 3/4] partially fix #2077: pmgsh: remove dependency on Term::ReadLine
Date: Mon, 22 Sep 2025 11:47:36 +0200	[thread overview]
Message-ID: <20250922114736.7fbcbdc9@rosa.proxmox.com> (raw)
In-Reply-To: <91adf303-d6df-4701-9ccf-58476691d9e9@proxmox.com>

On Fri, 19 Sep 2025 10:41:45 +0200
Fiona Ebner <f.ebner@proxmox.com> wrote:

> Am 18.09.25 um 10:58 PM schrieb Stoiko Ivanov:
> > Thanks for tackling this!
> > 
> > applied the patch for pve-common and played around a bit with pmgsh - and
> > yes - I did miss the completion (not the history though.. and am not sure
> > if I overlooked some other readline feature that would be lost)
> > 
> > but this reminded me of pvesh and that we dropped interactive mode at some
> > point (around PVE 5.2) there:
> > https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=cfc6a662938b90069e6c70b8112021a4554bad27
> > and the rationale of using bash for completion (still) sounds sensible.  
> 
> Oh, that dropped the REPL-style interface completely. If we do want to
> go ahead with dropping Term::ReadLine for pmgsh, I think we should do
> that here too.

Dropping the REPL-style interface should be fine - AFAIK `pmgsh` is
certainly used by our user-base to script some changes, but I don't expect
anyone to use it for daily work (and not being happy of using with
bash-completion instead of the REPL)

Had a chat with Thomas off-list - and he correctly pointed out that
dropping Term::ReadLine as dependency can be a nice2have, but it does not
hurt us currently - so there is no rush in getting this in.

Fixing #6748 OTOH is something affecting users, and it's also independent
of changing pmgsh.

So I think it's definitely worth to include 1/2, 2/2 (and the patch for
pve-common independent of whether or not we bring changes from pvesh to
pmgsh)

> 
> > did not look closer at what pmgsh is still missing from pvesh (the latter
> > saw quite a bit more changes in the past years) - but currently this seems
> > to be a good alternative.
> > (I'm not sure if I'll get to checking this in the upcoming 1-2 weeks, but
> > could try if you are busy elsewhere and noone else steps up)  
> 
> Do you have an example for what (potential) features you have in mind
> here? Or just looking through all pvesh changes and see what would be
> nice to have for pmgsh too?
was thinking about looking at the pvesh changes - but from a quick look
one example is `get /nodes/<other node>/journal` (it returns an array and
we don't handle that yet in pmgsh).
This would all mostly be improvements to the current status - the one
thing that I'd consider a regression with your patch vs. w/o is the lack
of completion.

> 
> > FWIW - tried registering an acme account (patch 1/4) - also worked fine.  
> 
> Would you mind adding a T-b there :)?
sent for 1/4, 2/4 and the pve-common patch :)


_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel


  reply	other threads:[~2025-09-22  9:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18 14:19 [pmg-devel] [PATCH-SERIES pmg-api 0/3] fix #2077: " Fiona Ebner
2025-09-18 14:19 ` [pmg-devel] [PATCH pmg-api 1/4] partially fix #2077: pmgconfig: " Fiona Ebner
2025-09-22  9:47   ` Stoiko Ivanov
2025-09-18 14:19 ` [pmg-devel] [PATCH pmg-api 2/4] partially fix #2077: pmgcm: " Fiona Ebner
2025-09-22  9:46   ` Stoiko Ivanov
2025-09-18 14:19 ` [pmg-devel] [PATCH pmg-api 3/4] partially fix #2077: pmgsh: " Fiona Ebner
2025-09-18 20:58   ` Stoiko Ivanov
2025-09-19  8:41     ` Fiona Ebner
2025-09-22  9:47       ` Stoiko Ivanov [this message]
2025-09-18 14:19 ` [pmg-devel] [RFC pmg-api 4/4] d/control: remove libterm-readline-gnu-perl dependency Fiona Ebner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250922114736.7fbcbdc9@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=f.ebner@proxmox.com \
    --cc=pmg-devel@lists.proxmox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal