umiswing umiswing
greneholt
/ QWERTY no option.keylayout
Created
June 30, 2023 19:17
Mac QWERTY keyboard layout without bindings for the option key. This disables the annoying default behavior of key combinations like option+i that enters diacritic mode and prevents using such shortcuts in VS Code.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE keyboard SYSTEM "file://localhost/System/Library/DTDs/KeyboardLayout.dtd"> | |
| <keyboard group="0" id="5000" name="QWERTY no option" maxout="1"> | |
| <layouts> | |
| <layout first="0" last="0" modifiers="48" mapSet="312" /> | |
| </layouts> | |
| <modifierMap id="48" defaultIndex="0"> | |
| <keyMapSelect mapIndex="0"> | |
| <modifier keys="" /> | |
| </keyMapSelect> |
algal
/ colorize-emacs.bashsource
Last active
March 28, 2025 16:15
Setting up truecolor (24 bit color) in emacs in the terminal, under iTerm2, blink.sh, and others.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # sourcing this file will define a bash functions that | |
| # tries to run subsequent calls to emacs with 24 bit color. | |
| # | |
| # It sets TERM=xterm-emacs-leg if | |
| # - we've created a user-local terminfo record for xterm-emacs-leg, and | |
| # - we're using iTerm2 or something has set COLORTERM=truecolor | |
| # | |
| # This will cause emacs to use 24 bit color only when it will work, | |
| # inside or outside of tmux. I haven't found a way to auto-detect Blink.sh yet. | |
| # |
socantre
/ CMakeLists.txt
Created
August 24, 2015 03:45
Example of using add_custom_command and add_custom_target together in CMake to handle custom build steps with minimal rebuilding: This example untars library headers for an INTERFACE library target
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| set(LIBFOO_TAR_HEADERS | |
| "${CMAKE_CURRENT_BINARY_DIR}/include/foo/foo.h" | |
| "${CMAKE_CURRENT_BINARY_DIR}/include/foo/foo_utils.h" | |
| ) | |
| add_custom_command(OUTPUT ${LIBFOO_TAR_HEADERS} | |
| COMMAND ${CMAKE_COMMAND} -E tar xzf "${CMAKE_CURRENT_SOURCE_DIR}/libfoo/foo.tar" | |
| COMMAND ${CMAKE_COMMAND} -E touch ${LIBFOO_TAR_HEADERS} | |
| WORKING_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/include/foo" | |
| DEPENDS "${CMAKE_CURRENT_SOURCE_DIR}/libfoo/foo.tar" |