If you want to get more information, I suggest you browse raspberry-pi-pcie-devices and its issue.
Use cases
| CM4 IO Board(Official) | CM4-IO-BASE-A(Waveshare) |
If you want to get more information, I suggest you browse raspberry-pi-pcie-devices and its issue.
Use cases
| CM4 IO Board(Official) | CM4-IO-BASE-A(Waveshare) |
| (use-package polymode | |
| :ensure t | |
| :defer t | |
| :hook (vue-mode . lsp-deferred) | |
| :mode ("\\.vue\\'" . vue-mode) | |
| :config | |
| (define-innermode poly-vue-template-innermode | |
| :mode 'html-mode | |
| :head-matcher "^<[[:space:]]*\\(?:template\\)[[:space:]]*>" | |
| :tail-matcher "^</[[:space:]]*\\(?:template\\)[[:space:]]*>" |
| class Workout < ApplicationRecord | |
| belongs_to :sport | |
| scope :most_recent_by_sport, -> do | |
| from( | |
| <<~SQL | |
| ( | |
| SELECT workouts.* | |
| FROM workouts JOIN ( | |
| SELECT sport_id, max(created_at) AS created_at |
xhost + ${hostname} to allow connections to the macOS host *export HOSTNAME=`hostname`* environment:
| README.el | |
| backups/ | |
| elpa/ | |
| projectile-bookmarks.eld | |
| recentf | |
| smex-items |
I got tired on creating new files manually for each new post a write so I put together this little command line task with Thor.
It creates a new file in the _posts directory with today’s date, parses the parameters to command as the post’s title and adds that as a slug to the new file. It then writes a default yaml template to the file (as specified in the script).
Running thor jekyll:new New and shiny post will for example create the file _posts/2012-12-28-new-and-shiny-post.markdown, populate it with an yaml template and finally open the file in my favorite editor.
Add the following to your Gemfile:
| function getHightlightCoords() { | |
| var pageIndex = PDFViewerApplication.pdfViewer.currentPageNumber - 1; | |
| var page = PDFViewerApplication.pdfViewer.getPageView(pageIndex); | |
| var pageRect = page.canvas.getClientRects()[0]; | |
| var selectionRects = window.getSelection().getRangeAt(0).getClientRects(); | |
| var viewport = page.viewport; | |
| var selected = selectionRects.map(function (r) { | |
| return viewport.convertToPdfPoint(r.left - pageRect.x, r.top - pageRect.y).concat( | |
| viewport.convertToPdfPoint(r.right - pageRect.x, r.bottom - pageRect.y)); | |
| }); |
New Coffeescript programmers usually struggle with understanding the differences between -> and => function definitions. In order to clarify this common case of confusion, it helps to look at how such functions are compiled down to JavaScript.
class A
constructor: () ->
@funcA()
@funcB()
funcA: () ->