Add comment to terminal when uploading a file

[jonathangroves]

I use Core Shell extensively to upload files to a number of dev servers, in amongst other remote tasks on the command line. I would find it very useful, when looking back at the remote terminal, to be able to see at what point I uploaded a file to that machine.
I suggest adding a comment as a command line entry on the remote terminal (in the case of a Linux terminal, preceded by the # character) and adding the date and time, plus the full path of the source and destination file.
Perhaps others would find it useful to be able to see the same for downloading files as well.
And of course, it should be optional.

Keep safe,

Jonathan

[yang (Yang.Y)]

@jonathangroves

I suggest adding a comment as a command line entry on the remote terminal (in the case of a Linux terminal, preceded by the # character) and adding the date and time, plus the full path of the source and destination file.

I have been thinking about add a comment for the up/download entry these days. It's easy to add such info, the problem is how to show it to user without clutter the UI.

All solutions I can think of is add an inspector for the up/download entry, it's a similar view as remote shell's Inspector, but concerned with SFTP information like local path, remote path, as well as timestamp.

The inspector could contain connection log which can help user diagnoses transfer problems.

In this way, the user interface could keep neat, while all essential information have a centralized place.

Please share you thoughts if you have any suggestions on UI design.

Thank you very much,

Yang

[jonathangroves]

Hi Yang.
Hoping you and yours are safe and well.
Sorry for the delay replying.
I am getting really desperate for some way of knowing an upload has failed as previously mentioned elsewhere. Some days I waste a lot of time trying to understand why a change has not succeeded only to realise the upload failed.
My concept was that CoreShell would type a comment to the command prompt the other end like this:
# index.html uploaded OK at 15:22.12
... so that the user would see this in the remote terminal session. I know that for some users this would not be useful, so perhaps it could be enabled in the Profile for each connection?
But your idea of an inspector could work, although I am not sure what it would look like or how it would be accessed...
Keep safe,
Jonathan

[yang (Yang.Y)]

@jonathangroves

My concept was that CoreShell would type a comment to the command prompt the other end like this:
# index.html uploaded OK at 15:22.12

It's not practical, the transfer task is detached from terminal session after created, you can resume a transfer task without open any remote sessions.

My understanding is this proposal trying to suggest a solution for the problem you have mentioned in this post:

Upload File Failing Without Warning

@yang PLEASE can I make another request for some sort of warning within Core Shell when an upload fails? This happens to me several times a day because the remote folders resynchronise with a repository regularly and I have to change permissions again to allow me to upload edited files. It seems very strange that this facility does not exist at the moment unless I make Core Shell go into the background. Keep safe, Jonathan

For transfer failing in-app notifications, I decided to add a bezel notify like this:

It should grab enough attention and also won't break the flow.

Kindly Regards,

Yang

[jonathangroves]

Thanks, Yang.
That notification look perfect for the other issue, thanks very much.
The purpose of this suggestion was not only to help with the other problem, but to help the user see at a glance that something was uploaded at a specific point within a terminal session. I'll make a external key macro in the amazing Keyboard Maestro to do this, no worries.
Keep safe,
Jonathan