Background: VBA macro can have a defined key binding that launches the macro. We don't import that key-binding at the moment. Well actually import all the information be we unfortunately discard it. For example if we had a Macro named 'launchByKey' in and Excel spreadsheet that was bound to the key cntrl-p then this is what you would see in the VBA source code

      Attribute VB_Name = "Module1"
      Sub launchByKey()
         Attribute launchByKey.VB_Description = "cntrl-p launches the macro"
         Attribute launchByKey.VB_ProcData.VB_Invoke_Func = "p\n14"
         MsgBox "launched"
      End Sub

As you can see the special attribute line 'Attribute lauchByKey.VB_ProcData.VB_Invoke_Func = "p\n14"' gives all the necessary info we need ( ok, we also need to recognise which procedure that attribute applies to ). Note: Currently we do at least extract information associated with one type of 'Attribute' statement see

1) legacy filter

  filter/source/msfilter/svxmsbas.cxx ( SvxImportMSVBasic::extractAttribute )

2) oox filter

  source/ole/vbamodule.cxx ( VbaModule::extractOleOverrideFromAttr )

In LibreOffice it is possible to provide a document only key configuration ( see the Tools|Customize|Keyboard dialog ) where a key|macro binding can be created. Finding the source code for that dialog will no doubt show how to create such a binding.