[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Hyperbole-users] Pointers to create modification on link-to-mail
From: |
Robert Weiner |
Subject: |
Re: [Hyperbole-users] Pointers to create modification on link-to-mail |
Date: |
Mon, 5 Aug 2019 21:19:40 -0400 |
If you could explain how those Org mode choices work, that would help us think
about your use case as well. I don’t fully follow what they do or how they
work.
-- Bob
> On Aug 5, 2019, at 9:16 PM, Robert Weiner <address@hidden> wrote:
>
> You are in luck. What you seem to want is a cross between Hyperbole explicit
> and implicit buttons and the next release of Hyperbole provides this in the
> form of labeled implicit buttons, where an explicit button type label (but
> with <[square bracket]> delimiters) can precede the implicit pattern that
> provides the parameters for the button. Or you could do this with the
> current implicit button mechanism as one implicit button type can handle any
> number of implicit buttons with different in-buffer parameters. Read the
> hibtypes.el definitions and I think you will get it. If you want to try the
> latest pre-release, install the code from the 7.0.3a git branch of the
> Hyperbole source at savannah.gnu.org or github.com/rswgnu/hyperbole.
>
> -- Bob
>
>> On Aug 5, 2019, at 9:02 PM, Jean Louis <bugs@gnu.support> wrote:
>>
>> * Robert Weiner <address@hidden> [2019-08-06 01:31]:
>>> I would leave the implicit button definition alone and just edit the
>>> defact action type in hactypes.el. That is, write your own version
>>> that overrides the builtin version after Hyperbole is loaded. Then
>>> you can just define that as you would a regular function and either
>>> throw up a menu with choices or dispatch based on context as you
>>> like.
>>
>> Yes thank you.
>>
>> But I am thinking how that has to be automated. Let me compare that to
>> Org links which has customization just for links:
>>
>> Hide Org Link Abbrev Alist:
>> INS DEL Cons-cell:
>> Protocol: gpatent
>> Choice: Value Menu Format: https://www.google.com/patents/US%s
>> INS DEL Cons-cell:
>> Protocol: xau2usd
>> Choice: Value Menu Format:
>> https://duckduckgo.com/?q=%s+xau+to+usd&ia=currency
>> INS DEL Cons-cell:
>> Protocol: geo
>> Choice: Value Menu Format: geo:%s
>> INS DEL Cons-cell:
>> Protocol: contact-id
>> Choice: Value Menu Function: view-contact
>> INS
>> State : EDITED, shown value does not take effect until you set or save it.
>> Alist of link abbreviations. More
>>
>> Thus I am proposing that you add explicit buttons type that can be
>> created in the form:
>>
>> <(attribute:value)> but also <(attribute value)> version, or even
>> <(attribute value1 value2 ...)>
>>
>> whereby such buttons can be easily customized in similar fashion as
>> Org links. That could be so much liberating from slower Org mode links
>> an it could work in any type of files.
>>
>> That opens numerous possibilities. If I have list of staff members in
>> the database, such database could be automatically expande into single
>> text file for reporting and review purposes. File would be opened in
>> specific directory for that staff member and buttons could be
>> generated automatically in that file.
>>
>> STAFF MEMBER REPORT (automatically generated)
>> ===================
>>
>> Mr. John Doe <(send email)>[1] - <(send SMS)> - <(call)>[2] - <(note)>
>>
>> Contact ID: <(1234)>[3]
>>
>> <(Emails address@hidden>)[4]
>> <(Emails address@hidden>)[5]
>> <(Emails address@hidden>)
>>
>> <(People introduced: 34)>[6]
>>
>> <(Assignments 143)>[7]
>>
>> <(Assignments done 89)>[8]
>>
>> <(Expenses Table)>[9]
>>
>> <(Notes)>[10]
>>
>> Footnotes:
>> [1] This would cause to send him email.
>>
>> [2] It would create new note for the contact.
>>
>> [3] This would open basic profile with contact information.
>>
>> [4] This would open all conversation related to person
>>
>> [5] This is type of button with attribute and value.
>>
>> [6] This button would be automatically generated and related to the
>> ID 1234 stored in the .hypb file, showing the list or report of
>> people that person has introduced.
>>
>> [7] It would open all assignments for the person, normally within Org
>> file.
>>
>> [8] It would show only DONE assignments
>>
>> [9] It would open expenses table.
>>
>> [10] It would show all the notes related to contact.
>>