Jekyll2025-12-26T04:43:02-08:00https://shinkocheng.github.io/feed.xmlshinkocheng.github.io(Fancy description to come soon!) Karabiner, XCode and Logitech Mice: Back/Forward Buttons2015-05-28T15:46:55-07:002015-05-28T15:46:55-07:00https://shinkocheng.github.io/workflow/2015/05/28/karabiner-xcode-logitech-mouseFinally got around to understanding Karabiner’s private.xml reference guide. This was the result.

There are three items, mapping buttons 4 and 5 to the keyboard command to “go back” or “go forward” Terminal, Chrome and all other applications, and home/end keys to the keyboard commands specific for Chrome Remote Desktop.

<?xml version="1.0"?>
<root>
  <appdef>
    <appname>XCODE</appname>
    <equal>com.apple.dt.Xcode</equal>
  </appdef>
  <appdef>
    <appname>TERMINAL</appname>
    <equal>com.apple.Terminal</equal>
  </appdef>
  <windownamedef>
    <name>GOOGLECRD</name>
    <regex>- Chrome Remote Desktop</regex>
  </winownamedef>
  <windownamedef>
    <name>GOOGLEMAIL</name>
    <regex>Inbox</regex>
  </windownamedef>
 
  <item>
    <name>Shinko's Custom</name>
    <item>
      <name>Use Button4/Button5 as Back/Forward except XCode</name>
      <identifier>private.back_forward_with_exceptions</identifier>
      <block>
        <autogen>__PointingButtonToKey__ PointingButton::BUTTON4,
          KeyCode::BRACKET_LEFT, ModifierFlag::COMMAND_L</autogen>
        <autogen>__PointingButtonToKey__ PointingButton::BUTTON5,
          KeyCode::BRACKET_RIGHT, ModifierFlag::COMMAND_L</autogen>
        <not>XCODE</not>
        <windowname_not>GOOGLECRD</windowname_not>
      </block>
      <block>
        <autogen>__PointingButtonToKey__ PointingButton::BUTTON4,
          KeyCode::CURSOR_LEFT, ModifierFlag::COMMAND_L | ModifierFlag::CONTROL_L</autogen>
        <autogen>__PointingButtonToKey__ PointingButton::BUTTON5,
          KeyCode::CURSOR_RIGHT, ModifierFlag::COMMAND_L | ModifierFlag::CONTROL_L</autogen>
        <only>XCODE</only>
      </block>
      <block>
        <autogen>__PointingButtonToKey__ PointingButton::BUTTON4,
          KeyCode::CURSOR_LEFT, ModifierFlag::OPTION_L</autogen>
        <autogen>__PointingButtonToKey__ PointingButton::BUTTON5,
          KeyCode::CURSOR_RIGHT, ModifierFlag::OPTION_L</autogen>
        <windowname_only>GOOGLECRD</windowname_only>
      </block>
    </item>
    <item>
      <name>Replace home/end keys with command-left/command-right</name>
      <identifier>private.home_end_with_exceptions</identifier>
      <block>
        <autogen>__KeyToKey__ KeyCode::HOME, KeyCode::CURSOR_LEFT | ModifierFlag::COMMAND_L</autogen>
        <autogen>__KeyToKey__ KeyCode::END, KeyCode::CURSOR_RIGHT | ModifierFlag::COMMAND_L</autogen>
        <windowname_not>GOOGLECRD</windowname_not>
        <not>TERMINAL</not>
      </block>
    </item>
    <item>
        <name>Use cmd and ctrl synonymously in Chrome Remote Desktop</name>
        <identifier>private.cmd_ctr_synonyms</identifier>
    <autogen>__KeyToKey__ KeyCode::SPACE | ModifierFlag::COMMAND_L, KeyCode::SPACE, ModifierFlag::COMMAND_L</autogen>
        <autogen>__KeyToKey__ KeyCode::COMMAND_L, KeyCode::CONTROL_L</autogen>
    <windowname_only>GOOGLECRD</windowname_only>
    </item>
  </item>
</root>
]]>X11 connection rejected because of wrong authentication after `sudo` to another user2014-08-31T15:46:55-07:002014-08-31T15:46:55-07:00https://shinkocheng.github.io/workflow/2014/08/31/x11-connection-rejected-after-sudo-to-another-userThis is a posting for my reference. I lifted this from Jianming Li in case one of these days he decides to take it down.

Cause: X win cookie not carried over after sudo login as another user.

Solution: Add the cookie to the other user.

From user1

$ echo $DISPLAY
localhost:10.0

$ xauth list
box.my.com/unix:10  MIT-MAGIC-COOKIE-1  4f76c629f8cdbf26ce4ae646cc24448c
box.my.com/unix:11  MIT-MAGIC-COOKIE-1  1acd10ab0fd098a86aba7aa691d7c067
box.my.com/unix:12  MIT-MAGIC-COOKIE-1  e007ee6844c417a6b866d66c7bbcbc7d

From User2 (even root)

]]>Scroll through screen buffer in MacOS Terminal2013-09-04T15:46:55-07:002013-09-04T15:46:55-07:00https://shinkocheng.github.io/workflow/2013/09/04/scroll-thru-screen-buffer-in-mac-terminalI use screen a lot for work. but when i want to see the history in terminal, typing ^a-[ and then up/down arrow gets tedious in a heartbeat. i discovered recently that you can put the following command in the ~/.screenrc file in the machine where screen is run, and you’ll have the capability to scroll through the history.

# Make xterm scrolling work properly with screen
termcapinfo xterm-256color|xterm-color|xterm|xterms|xs|rxvt ti@:te@
]]>Theory, Model, Data2011-11-18T14:46:55-08:002011-11-18T14:46:55-08:00https://shinkocheng.github.io/research/2011/11/18/theory-model-dataA successful research project requires 3 components: Theory, Model and Data. The definitions of these words from conversations with others are these.

Theory is the concept or idea that leveraged or to be tested (demonstrated).

Model is the system or a series of processes such as an algorithm that implements or tests (demonstrates) the theory.

Data is the test results demonstrating the efficacy of using the model, thereby also confirming the theory.

In the paper on Shape-Carving by Kutulakos, the theory is the principle of having each ray of light from the surface of the object agree in color, and by starting with a volume larger than the actual volume of the object and carving away voxel by voxel, the outcome is necessarily an overestimate of the actual object volume. The model is the algorithm that implements the shape-carving algorithm. The data are the volumetric reconstructions resulting from this method as well as any special parameter value used in the tests. Since the data shows that the method can compute the volumetric reconstructions successfully, the data also confirms the theory that reconstructions can be obtained by carving away at a volume larger than the actual object by keeping only voxels that agree in color among its many camera projections.

Data doesn’t come cheaply.

]]>