Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Forward Inbox/Outbox Message #172

Open
virtualghetto opened this issue Mar 13, 2015 · 1 comment
Open

Feature request: Forward Inbox/Outbox Message #172

virtualghetto opened this issue Mar 13, 2015 · 1 comment

Comments

@virtualghetto
Copy link

Personally, I think forwarding an existing inbox or outbox message is a better alternative than having a BCC or CC feature in Pond (which, for the record, I am not in favor of).
I think a forward option keeps with the spirit of pond.

The scenario would be as follows:
If the user wishes to send the same message to multiple recipients, the user would select the first contact, compose, draft and send to the first recipient.
Once in the outbox for that message, the user can type "forward (bob)" and that will take the user back to the draft stage, with exact the same message, but for a the new contact, bob. From there the user can send, and repeat the process for all of the intended recipients.
No information about previous or future recipients of that message can be leaked.

Thank you.

@burdges
Copy link
Contributor

burdges commented Mar 17, 2015

There was an effort to add a replies to outbox messages #126 It's not the same thing, but morally similar, and shows you how to do it if you want to do it for your own client.

There is a slight issue that the CLI's design makes commands that operated on two objects slightly counter intuitive, but that's not a big deal.

If @duy ever talks me into messing with #126 then I'd probably make at least the GUI do what you want too, but I'm not in Berlin these days. ;)

Also the TODO list on #161 once included the ability to change the destination of a draft in the CLI, so if that ever happens then this become even easier to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants