GNU bug report logs -
#23642
24.5; Dired Line Movement, Region Handling
Previous Next
Reported by: Michael Cain <cain.michael1 <at> gmail.com>
Date: Sat, 28 May 2016 22:45:02 UTC
Severity: minor
Found in version 24.5
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#23642: 24.5; Dired Line Movement, Region Handling
which was filed against the emacs package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 23642 <at> debbugs.gnu.org.
--
23642: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23642
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
>> (I'm not sure if this is actually a bug or not, just because Dired is
>> used so frequently and I assume someone probably would've mentioned it
>> by now. Hopefully this feedback will be helpful anyway)
>>
>> I find myself using the writable feature of Dired rather frequently, but
>> one default of Dired's up/down movement (specifically the shift
>> selection in Transient Mark mode) is difficult to work around. That is,
>> I very often try to hold down shift and proceed down lines to create a
>> region, but this doesn't work by default.
>>
>> I've temporarily solved this by making wrapper functions around
>> `dired-next-line' and `dired-previous-line' that handle the shift
>> selection, but it also works to add an additional "^" argument to the
>> existing "p" in those functions.
>>
>> Thanks! :)
>
> You are right. Shift-selection should be supported in WDired by this patch.
Thanks for the suggestion. Pushed to master.
> BTW, do you think that in WDired it would be more useful to select
> rectangular regions because file names are organized in columns.
> Then, for example, ‘downcase-region’ and ‘upcase-region’ will work
> on the selected regions, not fail are they do now in WDired.
[Message part 3 (message/rfc822, inline)]
(I'm not sure if this is actually a bug or not, just because Dired is
used so frequently and I assume someone probably would've mentioned it
by now. Hopefully this feedback will be helpful anyway)
I find myself using the writable feature of Dired rather frequently, but
one default of Dired's up/down movement (specifically the shift
selection in Transient Mark mode) is difficult to work around. That is,
I very often try to hold down shift and proceed down lines to create a
region, but this doesn't work by default.
I've temporarily solved this by making wrapper functions around
`dired-next-line' and `dired-previous-line' that handle the shift
selection, but it also works to add an additional "^" argument to the
existing "p" in those functions.
Thanks! :)
This bug report was last modified 8 years and 353 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.