Hi, Modi, I try to apply you config into Org Radio Tables.
Like this:
,
| #+ BEGIN RECEIVE ORGTBL test-table-comment-column
| | a | b |
| | 1 | 2 |
| #+ END RECEIVE ORGTBL test-table-comment-column
|
| #+ORGTBL: SEND test-table-comment-column orgtbl-to-orgtbl :splice nil :skip 0
| | / | <#>
Michael Brand writes:
> In the meantime I tried a changed org-activate-links
>
> #+begin_example
> - (visible-start (or (match-beginning 4) (match-beginning
> 2)))
> + (visible-start (or (match-beginning 4) start))
> -
Hi all,
I've made some improvements to my experimental "org-agenda-ng" project
which might be interesting to some of you. It also works as a kind of
"query language" for Org files, providing a lispy DSL to
match/filter/select entries in Org files. It's on GitHub at:
Hi Nicolas
On Thu, May 10, 2018 at 6:27 PM, Nicolas Goaziou wrote:
> IIUC, you want fontification to make it obvious there are square
> brackets in links, so that you know when they can be removed, for
> improved readability outside Org.
Yes, and generally just to see
(add-hook 'org-mode-hook 'alpha-eldoc-help-echo-mode)
;; fixme in elisp we want both link eldoc and elisp eldoc
(defun hoka-eldoc-help-echo-at-point ()
"Eldoc thingy for help-echo text properties."
(let ((val (get-text-property (point) 'help-echo)))
val))
(defun alpha-eldoc-help-echo-mode
Michael Brand writes:
> Only when I can see the brackets of case 3 in Org rendered as
> : [[https://en.wikipedia.org/wiki/Filter]]
> I know that I can change it to
> : https://en.wikipedia.org/wiki/Filter
> for a cleaner view in non-Org tools.
>
> For case 1 I still
Hi Nicolas
On Thu, May 10, 2018 at 3:33 PM, Nicolas Goaziou wrote:
> Sorry for being dense, but I still don't get it.
I can not claim to have been clear enough, hope to make it clearer below.
> When using non-Org tools, the solution doesn't belong to Org, does it?
> I
Michael Brand writes:
> Because I care about the raw file content that I see when using
> non-Org tools like mainly git but also diff, grep, less, vi and
> whatever.
Sorry for being dense, but I still don't get it.
When using non-Org tools, the solution doesn't
Hi Nicolas
On Thu, May 10, 2018 at 2:44 PM, Nicolas Goaziou wrote:
> I still don't understand what your use case is about. Why do you care
> about the presence of square brackets?
Because I care about the raw file content that I see when using
non-Org tools like mainly
Michael Brand writes:
> My use case is different, see above, and I don't like to move point or
> mouse for my use case.
I still don't understand what your use case is about. Why do you care
about the presence of square brackets?
It is difficult to think about the
Hi Nicolas
Thank you for looking into this.
On Thu, May 10, 2018 at 10:14 AM, Nicolas Goaziou
wrote:
> Just move the mouse over them. A tooltip or the minibuffer will display
> what the link is really.
During my use case I don't care what URL the link opens. I want to
On Thursday, 10 May 2018 at 10:14, Nicolas Goaziou wrote:
> Michael Brand writes:
[...]
>> As you know and can see above 1) to 3) can not be distinguished when
>> rendered with the default of org-descriptive-links t.
>
> Just move the mouse over them. A tooltip or
Hello,
Michael Brand writes:
>
> For the four different Org link "bracket-types" shown below I would
> like to have four different faces to be able to distinguish them at
> first sight. What is the recommended way to do this?
This is not possible. I'm not even sure
In my $dayjob we're now calling that "drinking our own champagne", which IMO is
rather nicer than eating our own dog food :-)
Best wishes - Neil
On 9 May 2018 19:11:21 BST, Jon Snader wrote:
>This is excellent. I love that, as Nicolas says, we're eating our
>own
>dog food.
Hi all
For the four different Org link "bracket-types" shown below I would
like to have four different faces to be able to distinguish them at
first sight. What is the recommended way to do this?
The four Org link bracket-types by example:
Buffer raw content (or visible-mode):
: 1)
15 matches
Mail list logo