[ESS] Losing Mark in Knitr block

[Steve Lianoglou]

Sorry for spamming :-)

Small update: it turns the bit about this highlight behavior only
effecting the "form" and not the "function" isn't quite right.

Although somehow this lost highlighting doesn't affect killing and
yanking text, other more mundane things are hosed. For instance, if I
make one of these moves and simply hit backspace or some other
character (to nuke the whole chunk from the point to the beginning of
the selection/mark) it acts as if there is no selection and just acts
as a solitary backspace/keystroke.

-steve


On Sat, Aug 16, 2014 at 3:18 PM, Steve Lianoglou
<lianoglou.steve at gene.com> wrote:
> I'd like to thank the folks who replied to me off list, and want to
> summarize the state of affairs.
>
> To summarize the issue: I've been using polymode for quite a while
> (love it) -- what prompted me to use it was because I liked the idea
> of using Rmarkdown (over Sweave) for quite some time, and polymode was
> the only game in town from the start.
>
> I'm also using emacs (24.whatever) exclusively via the terminal
> (either locally or on a remote server) (osx, iTerm2).
>
> Since the beginning of polymode time, this always happened to me:
>
> I'd set the mark (via ctrl-space) and move the point around to
> wherever I wanted to end the selection using either arrows, or ctrl-n,
> ctrl-p, whatever. As I was moving the point around, you'd see the
> active selection grow shrink as appropriate.
>
> If the point ever crossed a code chunk boundary (either I started the
> selection from a markdown section and crossed a "```{r}" boundary, or
> I started in a code section and crossed a "```" boundary), the
> highlight disappeared.
>
> Given that visual, I had thought my selection was lost, however it was
> pointed out to me that the mark/selection is still active even though
> the visual highlight is gone.
>
> Trying to copy (or whatever we call opt-w) the "what-I-thought-to-be"
> the obliterated selection and pasting it into the scratch buffer
> actually works -- even though the visual selection was gone,
> everything was still working as expected.
>
> So -- no real loss of functionality here, just loss of "form"
>
> For what it's worth, if I mark/make a selection by holding down shift
> and navigate to cover my selection using the arrow keys (shift
> remaining pressed down) then the highlight never gets nuked, even when
> it crosses markdown/code-chunk boundaries (also, how to I get shit-up
> to work?).
>
> Hopefully this recap might be useful for posterity.
>
> Thanks,
> -steve
>
>
> On Fri, Aug 15, 2014 at 2:01 PM, Steve Lianoglou
> <lianoglou.steve at gene.com> wrote:
>> Hi,
>>
>> On Thu, Aug 14, 2014 at 5:24 PM, Vitalie Spinu <spinuvit at gmail.com> wrote:
>>>  >>> Rob Richmond on Thu, 14 Aug 2014 14:10:13 -0700 wrote:
>>>
>>>  > When I set a mark outside of a knitr/sweave block <<>>= @ but then
>>>  > move in to the block, the mark gets deactivated. Is it possible to
>>>  > disable this behavior?
>>>
>>> Not in noweb mode. Polymode doesn't have this issue.
>>
>> Interesting -- we have this issue with Rmd files, though, when we
>> cross code chunk boundaries, right?
>>
>> Is it possible that this behavior will change for Rmd files in the future?
>>
>> ... or maybe we're talking about different things ... ?
>>
>> Thanks,
>> -steve
>>
>> --
>> Steve Lianoglou
>> Computational Biologist
>> Genentech
>
>
>
> --
> Steve Lianoglou
> Computational Biologist
> Genentech



-- 
Steve Lianoglou
Computational Biologist
Genentech