Just trying to articulate this, is this purely around import/export to a format (such as markdown) OR also for possibly facilitating viewing of say, markdown files sitting locally/on a locally-synced storage (e.g. dropbox) akin to obsidian (while still supporting the tracker format)?

Vaguely recall the latter idea mentioned in the discord some time ago.

Closing because we already have PR draft #1361

Closing because we already have PR draft #1361

API

• username - required
• :block/uid - optional
• :page/uid - optional, not in datascript (yet), just derived from :block/uid
• Constraints: 10 users max

v2

• click on avatar to follow that person
• show more context on hover

Screenshots

Closing because we already have #1361

• styling
  • can't use position absolute, use MUI popover/dropown
  • toggle disclosure - to show or not to show?
  • outliner for highlighting entire parent block
• keyboard interactions
  • pressing up right below a locked block
  • pressing backspace to join current with locked block
• mouse interactions
  • clicking on a locked block shouldn't go to edit mode for you
  • clicking on a block where parent block is locked

It seems that the strings for node completions are to long to be properly shown in the completion buffer.

Node:

:PROPERTIES:
:ID:       7bc23411-8e60-46df-9405-a5acd18100e0
:END:
#+title: AAAA
#+filetags: A B C D E F G H I J K

Completion Buffer:

As already two issues addressing the "problem" of displaying nodes in the minibuffer (#1553 #1530), I found it necessary to clarify the documentation.

Please see https://github.com/org-roam/org-roam/issues/1530#issuecomment-849437672

It seems that the strings for node completions are to long to be properly shown in the completion buffer.

Node:

:PROPERTIES:
:ID:       7bc23411-8e60-46df-9405-a5acd18100e0
:END:
#+title: AAAA
#+filetags: A B C D E F G H I J K

Completion Buffer:

Thanks!

As seen in there: Example taken from: https://lastpass.com/?ac=1&lpnorefresh=1

It is easy to copy a cell's contents to the clipboard. This is not so of the cell's output though. When I want to copy the output of a Pluto cell, I first need to select all of the output, which is difficult to do using my laptop's trackpad. Then, once I paste elsewhere, e.g. to GNU Emacs, I find that much of the punctuation is lost. My best guess is that when outputting Julia objects the punctuation characters come from a CSS stylesheet rather than the output content.

This is an accessability issue for me. Most of the Pluto user interface (hiding cells, and adding new cells are the only buttons I've found so far -- through painstaking examination of the DOM tree) is invisible if one's browser is in dark mode.

version clj-kondo v2021.06.18

macro usage clojure.test/are

platform

; java --version
openjdk 11.0.10 2021-01-19
OpenJDK Runtime Environment GraalVM CE 20.3.1 (build 11.0.10+8-jvmci-20.3-b09)
OpenJDK 64-Bit Server VM GraalVM CE 20.3.1 (build 11.0.10+8-jvmci-20.3-b09, mixed mode, sharing)

problem

Possible false positive on #636

Nested #()s are not allowed

repro

clj-kondo --lint test.clj

(ns test
  (:require [clojure.test :refer [deftest testing are]]))

(def coll [])

(deftest linter-tests
  (testing "Nested #()s are not allowed"
    (are [key pred] (every? #(pred (get % key)) coll)
      :events #(every? (fn [{:keys [id timestamp]}]
                         (and (string? id)
                              (pos-int? timestamp)))
                       %))))

config

{:linters
 {:unresolved-symbol
  {:exclude [(clojure.test/are [thrown? thrown-with-msg? thrown-with-data?])
             (clojure.test/is [thrown? thrown-with-msg? thrown-with-data?])
             (io.pedestal.interceptor.error/error-dispatch [ctx ex])]}}
 :lint-as {superlifter.api/def-fetcher      clojure.core/defrecord
           superlifter.api/def-superfetcher clojure.core/defrecord
           diehard.core/defretrypolicy      clojure.core/def
           mojito.test-util/with-system     clojure.core/let}}

When writing hooks, I noticed maps weren't supported, which I believe has to do with missing support for namespaced maps in rewrite-clj. I noticed #1039 was started to deal with this.

I think rewrite-clj has support for namespaced maps now, and probably exposing their constructor, and adding a resolver to sexpr, should be possible.

I'm willing to try to hack on this, if that helps, assuming the bundled version of rewrite-clj is up to date.

Everything in the general settings tab is disabled

Syntax Highlight 2.0.8 (40) macOS 11.4

Turns out using `file:///readonlydir/notebook.jl didn't work either. Seems not to be recognized as a URL and is instead treated as a relative path.

Trying to open /readonlydir/notebook.jl where the user has no write permissions for /readonlydir produces:

SystemError: opening file "/readonlydir/notebook backup 1.jl": Permission denied

I guess a backup in /tmp isn't really a backup, but maybe issuing a warning that no backup will be created or creating the backup under the users home directory (e.g. where notebooks are saved by default) would be better so that the notebook can still be opened? Or maybe it has to be copied to a writable directory before opening? It would be preferable to avoid being unable to open the notebook altogether just because it lives in a read-only directory.

FWIW, copying from a read-only directory to a writable directory would provide a way to make "starter notebooks" that students could open and expand on. This is essentially what happens when opening a URL based notebook. I guess maybe a workaround is to use a file:// URL, but it would still be nice to do this with a pathname too.

That worked thanks

Hi:

Recently it has been commented in the emacs devel mailing list the interest to add tree-sitter support in vanilla.

https://lists.gnu.org/archive/html/emacs-devel/2021-06/msg00174.html https://lists.gnu.org/archive/html/emacs-devel/2021-06/threads.html

This module is a very good starting point for that and it was mentioned that a very good first step is that this packages become part of the official Elpa repo.

It would be very nice if the developers of the emacs-tree-sitter package join to the developer team and help with the integration too cause you already have the experience. The integration with vanilla can improve the user experience, simplify the installation "out of the box" experience while on the other hand we can provide a better support and functionalities to make it more efficient.

WDYT?

Let's keep the discussion on https://github.com/ubolonton/emacs-tree-sitter/discussions/127