[Tickets #13282] Re: Option/pref to make addresses more accessible to text tools
noreply at bugs.horde.org
noreply at bugs.horde.org
Thu Jun 26 16:44:36 UTC 2014
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/13282
------------------------------------------------------------------------------
Ticket | 13282
Updated By | horde at headbank.co.uk
Summary | Option/pref to make addresses more accessible to text
| tools
Queue | IMP
Version | Git master
Type | Enhancement
State | Rejected
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
horde at headbank.co.uk (2014-06-26 16:44) wrote:
>> In my use-case it is desirable to be able to copy the raw email
>> address of a sender, or an address that is written in an email.
>> However, in message views (preview pane and own window) the sender is
>> rendered by its text name (if present) so the actual address cannot
>> be copied without resorting to View Source.
>
> This is what the Copy to Clipboard option is for.
>
Sorry, can you elaborate on this? I don't see this anywhere as an
option, all I can find is this previously rejected ticket:
http://bugs.horde.org/ticket/12562
If I was aware of an option more usable than View Source, believe me,
our whole office would be using it.
>> I suggest a user pref and/or global configuration option whereby the
>> sender's raw address is displayed onscreen (instead of or in addition
>> to the accompanying text name) in the message-view header, to
>> facilitate copying.
>>
>> I further suggest that this or a separate pref/config causes email
>> addresses in message bodies to be parsed not into Horde compose
>> links, but standard mailto: links, in order likewise to facilitate
>> copying of the address (not to mention being potentially advantageous
>> to heterogeneous MUA setups where Horde may be used for message
>> display but another MUA used for sending).
>
> If you disagree with the way addresses are handled, you can make
> changes to the UI display code.
I don't disagree with how it's handled OOTB, simply suggesting that a
pref to convert to MUA-agnostic syntax would be of value to my
use-case and possibly to others. But since you already rejected it,
there's not much chance for others to speak up.
More information about the bugs
mailing list