Re: Move selection up, down

Re: Move selection up, down

[Lennart Borgman (gmail)]

jiri.pejchal@gmail.com wrote:
> Hi,
> 
> in Netbeans when you press M-S-up/M-S-down you move the selected text
> up/down. When nothing is selected it moves the current line.
> 
> With C-S-up/C-S-down you copy the selection up/down. When nothings is
> selected it copies the current line up/down.
> 
> Is such functionality available in emacs?
> 
> Jiri Pejchal

Based on Jiri's question I suggest that the transpose-* commands should
be changed so that they transpose an active highlighted region according
to the amount given by the transpose-* name.

Any thoughts about that?

RE: Move selection up, down

[Drew Adams]

> > in Netbeans when you press M-S-up/M-S-down you move the 
> selected text
> > up/down. When nothing is selected it moves the current line.
> > 
> > With C-S-up/C-S-down you copy the selection up/down. When 
> nothings is
> > selected it copies the current line up/down.
> > 
> > Is such functionality available in emacs?
> > 
> > Jiri Pejchal
> 
> Based on Jiri's question I suggest that the transpose-* 
> commands should
> be changed so that they transpose an active highlighted 
> region according
> to the amount given by the transpose-* name.
> 
> Any thoughts about that?

Huh?

What will you do with `transpose-word', for instance, when there is an active
region? I don't follow the suggestion. How about some examples?

Re: Move selection up, down

[Lennart Borgman (gmail)]

Drew Adams wrote:
>>> in Netbeans when you press M-S-up/M-S-down you move the 
>> selected text
>>> up/down. When nothing is selected it moves the current line.
>>>
>>> With C-S-up/C-S-down you copy the selection up/down. When 
>> nothings is
>>> selected it copies the current line up/down.
>>>
>>> Is such functionality available in emacs?
>>>
>>> Jiri Pejchal
>> Based on Jiri's question I suggest that the transpose-* 
>> commands should
>> be changed so that they transpose an active highlighted 
>> region according
>> to the amount given by the transpose-* name.
>>
>> Any thoughts about that?
> 
> Huh?
> 
> What will you do with `transpose-word', for instance, when there is an active
> region? I don't follow the suggestion. How about some examples?

Move the next or previous word (depending on which side of the region
you are on) to the other side of the region. Is not that a natural
extension?

RE: Move selection up, down

[Drew Adams]

> > What will you do with `transpose-word', for instance, when 
> > there is an active region? I don't follow the suggestion.
> > How about some examples?
> 
> Move the next or previous word (depending on which side of the region
> you are on) to the other side of the region. Is not that a natural
> extension?

Dunno. I would expect it instead to swap the region and the next or previous
word, leaving the separator chars between them. `transpose-word' recognizes
intervening non-word chars (any number), and swaps the words around them.

Sounds OK to me, but I don't have much of a opinion one way or the other. It
might require users to sometimes deactivate the region to get today's effect,
but that's no biggee.

Presumably, the region would be kept active, so you could repeat the operation -
e.g. `transpose-line' would move the region down a line each time. (That's
another difference from today's commands - they deactivate the region.)

Either there used to be a command that moved the region this way or I had my
own, long ago. I remember using it, but I haven't missed it for many moon.

Re: Move selection up, down

[Lennart Borgman (gmail)]

Drew Adams wrote:
>>> What will you do with `transpose-word', for instance, when 
>>> there is an active region? I don't follow the suggestion.
>>> How about some examples?
>> Move the next or previous word (depending on which side of the region
>> you are on) to the other side of the region. Is not that a natural
>> extension?
> 
> Dunno. I would expect it instead to swap the region and the next or previous
> word, leaving the separator chars between them. `transpose-word' recognizes
> intervening non-word chars (any number), and swaps the words around them.

Isn't that the same thing?

> Sounds OK to me, but I don't have much of a opinion one way or the other. It
> might require users to sometimes deactivate the region to get today's effect,
> but that's no biggee.
> 
> Presumably, the region would be kept active, so you could repeat the operation -
> e.g. `transpose-line' would move the region down a line each time. (That's
> another difference from today's commands - they deactivate the region.)

Yes.

> Either there used to be a command that moved the region this way or I had my
> own, long ago. I remember using it, but I haven't missed it for many moon.
> 
> 
> 

RE: Move selection up, down

[Drew Adams]

> >>> What will you do with `transpose-word', for instance, when 
> >>> there is an active region? I don't follow the suggestion.
> >>> How about some examples?
> >> Move the next or previous word (depending on which side of 
> >> the region you are on) to the other side of the region.
> >> Is not that a natural
> >> extension?
> > 
> > Dunno. I would expect it instead to swap the region and the 
> > next or previous word, leaving the separator chars between
> > them. `transpose-word' recognizes intervening non-word chars
> > (any number), and swaps the words around them.
> 
> Isn't that the same thing?

It depends on what you meant. If that's what you meant, then it's the same
thing. ;-) 

But just moving the next or previous word to the other side of the region is
different from swapping their places around the separators.

region sep word

1. word region sep 
(word moved to other side of region)

2. word sep region
(word and region swapped around separator)

I thought perhaps you meant #1. I described #2.

Re: Move selection up, down

[Lennart Borgman (gmail)]

Drew Adams wrote:
>>>>> What will you do with `transpose-word', for instance, when 
>>>>> there is an active region? I don't follow the suggestion.
>>>>> How about some examples?
>>>> Move the next or previous word (depending on which side of 
>>>> the region you are on) to the other side of the region.
>>>> Is not that a natural
>>>> extension?
>>> Dunno. I would expect it instead to swap the region and the 
>>> next or previous word, leaving the separator chars between
>>> them. `transpose-word' recognizes intervening non-word chars
>>> (any number), and swaps the words around them.
>> Isn't that the same thing?
> 
> It depends on what you meant. If that's what you meant, then it's the same
> thing. ;-) 
> 
> But just moving the next or previous word to the other side of the region is
> different from swapping their places around the separators.
> 
> region sep word
> 
> 1. word region sep 
> (word moved to other side of region)
> 
> 2. word sep region
> (word and region swapped around separator)
> 
> I thought perhaps you meant #1. I described #2.

I think #1 would not be consistent with word definitions etc.

Re: Move selection up, down

[Jiri Pejchal]

On Wed, Aug 20, 2008 at 1:30 AM, Lennart Borgman (gmail)
<lennart.borgman@gmail.com> wrote:
> Drew Adams wrote:
>>>> What will you do with `transpose-word', for instance, when
>>>> there is an active region? I don't follow the suggestion.
>>>> How about some examples?
>>> Move the next or previous word (depending on which side of the region
>>> you are on) to the other side of the region. Is not that a natural
>>> extension?
>>
>> Dunno. I would expect it instead to swap the region and the next or previous
>> word, leaving the separator chars between them. `transpose-word' recognizes
>> intervening non-word chars (any number), and swaps the words around them.
>
> Isn't that the same thing?
>
>> Sounds OK to me, but I don't have much of a opinion one way or the other. It
>> might require users to sometimes deactivate the region to get today's effect,
>> but that's no biggee.
>>
>> Presumably, the region would be kept active, so you could repeat the operation -
>> e.g. `transpose-line' would move the region down a line each time. (That's
>> another difference from today's commands - they deactivate the region.)

Just to make it clear the netbeans implementation is actually only
line oriented.
If the selection span less than one line the move/copy operations
works on the line with cursor.
If the selection span more than one line it operates on those lines.

Alt-Shift Left/Right/Up/Down Shift lines left/right/up/down
Ctrl-Shift-Up/D Copy lines up/down

Jiri Pejchal

Re: Move selection up, down

[martin rudalics]

[-- Attachment #1: Type: text/plain, Size: 593 bytes --]

 > Just to make it clear the netbeans implementation is actually only
 > line oriented.
 > If the selection span less than one line the move/copy operations
 > works on the line with cursor.
 > If the selection span more than one line it operates on those lines.
 >
 > Alt-Shift Left/Right/Up/Down Shift lines left/right/up/down
 > Ctrl-Shift-Up/D Copy lines up/down

If you have Emacs 23 you can use the functions `m&d-drag-line-down' and
`m&d-drag-line-up' in the attached m&d.el file and add your key
bindings.  If you have Emacs 22 only I can try to find an older version
of this.

martin

[-- Attachment #2: m&d.el.gz --]
[-- Type: application/x-gzip, Size: 7630 bytes --]

Re: Move selection up, down

[Richard M. Stallman]

    Based on Jiri's question I suggest that the transpose-* commands should
    be changed so that they transpose an active highlighted region according
    to the amount given by the transpose-* name.

Maybe only C-t should do that.