Hi
I got an error as follow when I tried to export:
,
| org-babel-exp process R at line 5495...
| Evaluation of this R code-block is disabled.
| user-error: Unable to resolve link "*uLELFit"
`
I thought "OK - I'll search for uLELFit and just fix this link - but I
could do what I wanted,
Hi Rainer,
Rainer M Krug writes:
> I figured out that I can not search for text in the link.
>
> Thins is quite annoying, especially as I even thought of opening the
> file in another texteditor, search for the string, and save it again.
>
> As an example: if this link is in an org-mode file, A
Richard Lawrence wrote:
> Rainer M Krug writes:
>
>> I figured out that I can not search for text in the link.
>>
>> Thins is quite annoying, especially as I even thought of opening the
>> file in another texteditor, search for the string, and save it again.
>>
>> As an example: if this link is in
On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug wrote:
> Hi
>
> I got an error as follow when I tried to export:
>
> ,
> | org-babel-exp process R at line 5495...
> | Evaluation of this R code-block is disabled.
> | user-error: Unable to resolve link "*uLELFit"
> `
>
> I thought "OK - I'll
It would be nice to be able to search in links without extra work to change
modes. Without this, you cannot even search for a cite key!
-k.
Please excuse brevity. Sent from pocket computer with tiny non-haptic feedback
keyboard.
> On Mar 20, 2015, at 11:38, Jacob Gerlach wrote:
>
>> On
hmm:
===
search-invisible is a variable defined in `isearch.el'.
Its value is open
Documentation:
If t incremental search/query-replace can match hidden text.
A nil value means don't match invisible text.
When the value is `open', if the text matched is made invisible by
an overlay having an `inv
org-show-context-detail may also be relevant:
org-show-context-detail is a variable defined in `org.el'.
Its value is ((isearch . lineage)
(bookmark-jump . lineage)
(default . ancestors))
Documentation:
Alist between context and visibility span when revealing a location.
Some actions may move
On Fri, 20 Mar 2015, Ken Mankoff wrote:
It would be nice to be able to search in links without extra work to
change modes. Without this, you cannot even search for a cite key!
You *can* search in links without changing modes.
Exa RET
runs nonincremental-search-forward on "Exa" and finds
On 2015-03-21T01:59:07+1100, Richard Lawrence
said:
RL> I am not sure if this counts as a bug or not, so someone else
RL> should still address this question. Maybe this is the
desired RL> behavior, given that the link text is hidden? Or
maybe it's just RL> not possible to search in hidde
Hi Rainer,
In terms of searching through all open buffers,
here is what I use (helm and helm-multi-occur):
,
| (setq helm-M-x-requires-pattern 0)
|
| ;; http://emacs.stackexchange.com/a/740
| (require 'helm-regexp)
| (eval-after-load "helm-regexp"
| '(setq helm-source-moccur
| (hel
On Sat, Mar 21, 2015 at 7:34 PM, Alexis wrote:
>
> On 2015-03-21T01:59:07+1100, Richard Lawrence
> said:
>
> RL> I am not sure if this counts as a bug or not, so someone else
> RL> should still address this question. Maybe this is the desired
> RL> behavior, given that the link text is hidden?
Jacob Gerlach writes:
> On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug wrote:
>> Hi
>>
>> I got an error as follow when I tried to export:
>>
>> ,
>> | org-babel-exp process R at line 5495...
>> | Evaluation of this R code-block is disabled.
>> | user-error: Unable to resolve link "*uLELFit"
"Charles C. Berry" writes:
> On Fri, 20 Mar 2015, Ken Mankoff wrote:
>
>> It would be nice to be able to search in links without extra work to
>> change modes. Without this, you cannot even search for a cite key!
>
> You *can* search in links without changing modes.
>
> Exa RET
>
> runs nonin
Thanks everybody - many useful comments and ideas.
First I must say it makes sense to give the error message, although I
was quite surprised.
But the message should contain a string one can easily search for. And I
guess the most used search function is C-s I think the message should be
changes t
On Mon, Mar 23, 2015 at 8:45 AM, Rainer M Krug wrote:
> First I must say it makes sense to give the error message, although I
> was quite surprised.
>
> But the message should contain a string one can easily search for. And I
> guess the most used search function is C-s I think the message should
Rainer M Krug krugs.de> writes:
> > M-x occur RET Exa RET
>
> Ah - occur is nice - very nice. I like the output and also that it shows
> me all hits - I'll use this more often!
It even has a key binding: "M-s o". If you like a function and wonder if it
has a key binding: "C-h w RET" will tell
Achim Gratz writes:
> Rainer M Krug krugs.de> writes:
>> > M-x occur RET Exa RET
>>
>> Ah - occur is nice - very nice. I like the output and also that it shows
>> me all hits - I'll use this more often!
>
> It even has a key binding: "M-s o". If you like a function and wonder if it
> has a key
On 2015-03-20 at 13:53, Samuel Wales wrote:
> hmm:
>
> ===
> search-invisible is a variable defined in `isearch.el'.
> Its value is open
>
> Documentation:
> If t incremental search/query-replace can match hidden text.
> A nil value means don't match invisible text.
> When the value is `open', if
hi ken,
that's right, my point was that perhaps it is relevant, not that one
would set the variable.
for example, perhaps there is a way that timestamps can have an
invisible property and thus be subject to this variable.
of course, it might not be possible, if timestamps do not use
overlays, bu
19 matches
Mail list logo
