adam/contact
1
0 Fork 0
mirror of https://github.com/pdxlocations/contact.git synced 2026-10-31 00:01:57 +01:00
Code Issues 16 Packages Projects Releases Wiki Activity

CLI option to send a text via commandline #77

New Issue
Open
opened 2026-10-05 03:19:45 +02:00 by adam · 3 comments
adam commented 2026-10-05 03:19:45 +02:00
Owner
Copy link
Copy source

Love the app as its lightweight and provides everything in a TUI interface.
Is there any possiblity to integrate shell commands to get it s output for messages?

For example, to launch a simple command and get its STDOUT and put it into the message box. And the user can choose to send it.

Love the app as its lightweight and provides everything in a TUI interface. Is there any possiblity to integrate shell commands to get it s output for messages? For example, to launch a simple command and get its STDOUT and put it into the message box. And the user can choose to send it. <!-- github-sync-id:3878358224 -->
adam commented 2026-10-05 03:19:46 +02:00
Author
Owner
Copy link
Copy source

I like this idea. Could you provide me with some example commands you might enter?

What would we do with commands that return over the messages size limit?

I like this idea. Could you provide me with some example commands you might enter? What would we do with commands that return over the messages size limit? <!-- github-comment-id:3828833421 -->
adam commented 2026-10-05 03:19:47 +02:00
Author
Owner
Copy link
Copy source

May I suggest the following?

  • allow the message box to be highlighted
  • key stroke ctrl+! (Just like in VI) this brings up a command box.
  • enter the single line that would be run as a bash command (or what ever
    the default shell environment)
  • collect the STDIN that is generated within 30 seconds. (Kill the command
    otherwise)
  • show a size counter at the end of the message box. A simple “<1b” or the
    exact message size. Turn red if it exceeds. (Character count can also work?)

Is it also possible to show a cursor within the message box? So that one
can edit the message and shorten it if necessary.

Just some thoughts.

Thanks for considering.

On Sun, 1 Feb 2026 at 12:58 AM, pdxlocations @.***>
wrote:

pdxlocations left a comment (pdxlocations/contact#243)
https://github.com/pdxlocations/contact/issues/243#issuecomment-3828833421

I like this idea. Could you provide me with some example commands you
might enter?

What would we do with commands that return over the messages size limit?

—
Reply to this email directly, view it on GitHub
https://github.com/pdxlocations/contact/issues/243#issuecomment-3828833421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTF7LCUZ6BK3UOHWITYSYD4JTNKPAVCNFSM6AAAAACTQH4DE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYHAZTGNBSGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

May I suggest the following? - allow the message box to be highlighted - key stroke ctrl+! (Just like in VI) this brings up a command box. - enter the single line that would be run as a bash command (or what ever the default shell environment) - collect the STDIN that is generated within 30 seconds. (Kill the command otherwise) - show a size counter at the end of the message box. A simple “<1b” or the exact message size. Turn red if it exceeds. (Character count can also work?) Is it also possible to show a cursor within the message box? So that one can edit the message and shorten it if necessary. Just some thoughts. Thanks for considering. On Sun, 1 Feb 2026 at 12:58 AM, pdxlocations ***@***.***> wrote: > *pdxlocations* left a comment (pdxlocations/contact#243) > <https://github.com/pdxlocations/contact/issues/243#issuecomment-3828833421> > > I like this idea. Could you provide me with some example commands you > might enter? > > What would we do with commands that return over the messages size limit? > > — > Reply to this email directly, view it on GitHub > <https://github.com/pdxlocations/contact/issues/243#issuecomment-3828833421>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACTF7LCUZ6BK3UOHWITYSYD4JTNKPAVCNFSM6AAAAACTQH4DE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMRYHAZTGNBSGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > <!-- github-comment-id:3829724546 -->
adam commented 2026-10-05 03:19:48 +02:00
Author
Owner
Copy link
Copy source

This is how 'ircii' and similar chat clients do it... /exec <command> for no redirection, /exec -m <user/channel> <command> to direct output to user/channel, or /exec -o <command> to direct output to current channel/window.

By the way from the title of this issue, I thought it meant just being able to send a message from the command line without having to open the interface. Like "contact --send-msg <channel/node> <message>" from a prompt, it sends the message, then brings you back to a prompt.

This is how 'ircii' and similar chat clients do it... /exec \<command\> for no redirection, /exec -m \<user/channel\> \<command\> to direct output to user/channel, or /exec -o \<command\> to direct output to current channel/window. By the way from the title of this issue, I thought it meant just being able to send a message from the command line without having to open the interface. Like "contact --send-msg \<channel/node\> \<message\>" from a prompt, it sends the message, then brings you back to a prompt. <!-- github-comment-id:4095911994 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/contact#77