<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - Support for defining multiword commands at the command line"
   href="http://llvm.org/bugs/show_bug.cgi?id=18512">18512</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Support for defining multiword commands at the command line
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>lldb
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>enhancement
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>All Bugs
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>lldb-dev@cs.uiuc.edu
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>egranata@apple.com
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>From a thread on lldb-dev:

we need general facilities for multiword commands definition by users.
Something like

(lldb) command multiword add info

And then you should be able to tell any command-defining command (e.g. command
script add, command alias, command regex) that whatever command it is crafting,
it is actually a subcommand, e.g.

(lldb) command alias —subcommand info — break breakpoint list

That would cause a hierarchy to be created where there is a multiword “info”
command at the root, with a break subcommand, whose implementation is
breakpoint list

| -info
| —— break ==> breakpoint list

With that, you could easily define your info command hierarchy in your
.lldbinit and anyone who wants to define their own multiword commands
hierarchies would naturally be allowed to do so.

Needless to say, one should protect system commands, such that you could not
say

(lldb) command alias —subcommand process doevilthings “some other command here"

or

(lldb) command multiword add process

or worse

(lldb) command multiword delete process</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>