-
Notifications
You must be signed in to change notification settings - Fork 4
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
could the questions and answers have also a time stamp not only a delta time? #13
Comments
Probably. What if it was a mouseover like on http://bioconductor.org at the lower left under Support, if you mouse over the text "xx hours ago" it gives you an ISO8601 timestamp? |
This would not solve the issue. The whole idea is to have the timestamp visible as text that can be copied with the answer. With the js idea if I document an answer and keep it only in text format I lose the date unless I recalculate manually. I usually document my code or git commits with the url and a copy of the answers I found useful. The javascript option would not be of much help to me in these situations, I am afraid. |
Personally I'd like to see the search results displayed in the same format sas the main post lists, with the addition of highlighted text and with an additional 'Sort' option (by 'Relevance', on by default). Somehow this issue is related to issue 4. |
Thanks @mtmorgan, but probably your comment fit better with my issue 12 that is more tightly related with the issue 4 than this one. I think even if the sorting issues take some time to be improved, at least having the time (no matter the format) in the search output, allows you to manually prioritize the messages and would be a nice addition. |
Having a delta time (5 min ago, 3years ago) is nice and handy, but when you copy the answer and paste it in your diary or log for further documentation then it lose its function. I would find very useful to have also a real date so I could see when the answer was created when reading my logs or diary notes.
Is this something feasible?
The text was updated successfully, but these errors were encountered: