You are not logged in.
Nano's default behaviour of hard-wrappig lines can be quite dangerous for newbies, it can for example thrash grub lines easily when adding some text like vga=773 in combination with long uuid's. Shouldn't Nano better be packaged with 'set nowrap', and called with nano -w in the installer?
I can't think of many use cases for hard wrapping text anyway...
ᶘ ᵒᴥᵒᶅ
Offline
It seems like a safe thing to do.
Most stuff can be broken up though, like the modules array. Just be sure to add a space before the \
Offline
put
alias nano="nano -w"
in your .bashrc
Be yourself, because you are all that you can be
Offline
put
alias nano="nano -w"
in your .bashrc
yes i know that now, but not when i was installing arch. coming from ubuntu where hard-wrap is disabled by default, i had no idea i was about to prevent my computer from booting when i added some parameters to grub.
Last edited by litemotiv (2008-08-04 10:48:54)
ᶘ ᵒᴥᵒᶅ
Offline
Oh, the hard wrapping used to drive me mad. then I switched to emacs
Offline
Packaging nano without hardwrap isn't a very KISS approach. PKGs are supposed to be as vanilla as possible. But adding -w to the calls in the setup might be a good thing to do. File a bug report.
Haven't been here in a while. Still rocking Arch.
Offline
While I can see the point the OP is making, I feel that Arch should just go with whatever the developer default is.
Offline
While I can see the point the OP is making, I feel that Arch should just go with whatever the developer default is.
Offline
It seems that nowrap is now not available in nano. Is this as a result of an upstream change?
I had this aliased just as it is suggested previously here and so every time I typed "nano filename" I just got the help info. I've commented out the alias in my .bashrc so long but its a little silly.
I also had the "set nowrap" option set in /etc/nanorc but now I get an error every time I open nano:
brendan@watricky:~$ nano .bashrc
Error in /etc/nanorc on line 94: Unknown flag "nowrap"
Press Enter to continue starting nano.
pacman russian roulette: yes | pacman -Rcs $(pacman -Q | LANG=C sort -R | head -n $((RANDOM % 10)))
(yes, I know its broken)
Offline
@zatricky
I had the same error. I comment out the option in /etc/nanorc.
There was a change in the PKGBUILD:
http://repos.archlinux.org/viewvc.cgi/n … iew=markup
./configure --prefix=/usr --sysconfdir=/etc --enable-color --enable-nanorc --enable-multibuffer --disable-wrapping
Offline
But still there is this option available in /etc/nanorc ... But that's useless now, so it would be better to remove these two lines in this config as well
Offline
Lol. So it looks like the default is to not do any wrapping at all anyway now.
Thanks, sp42b
pacman russian roulette: yes | pacman -Rcs $(pacman -Q | LANG=C sort -R | head -n $((RANDOM % 10)))
(yes, I know its broken)
Offline
http://bugs.archlinux.org/task/11290, see the closing comment.
Last edited by Mr.Elendig (2008-09-05 13:08:55)
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
Nano's default behaviour of hard-wrappig lines can be quite dangerous for newbies...<snip>....I can't think of many use cases for hard wrapping text anyway...
I would suggest taking it up with the original Nano developers/maintainers. Our general policy is to keep the default settings from the source--they usually make such choices for a reason.
thayer williams ~ cinderwick.ca
Offline
I would suggest taking it up with the original Nano developers/maintainers. Our general policy is to keep the default settings from the source--they usually make such choices for a reason.
that makes absolutely no sense in this context thayer.
it's just a matter of running nano with the right parameter during arch-install, you can keep the package itself as vanilla as you want. "their" design reasons are per definition less valid than the specific circumstances we are using it for, in this case a crucial part of the installation process. for our scenario there is no point in using hard line breaks, but there are good reasons not to.
ᶘ ᵒᴥᵒᶅ
Offline
Arch Linux defines simplicity as a lightweight base structure without unnecessary additions, modifications, or complications, that allows an individual user to shape the system according to their own needs. In short; an elegant, minimalist approach.
If I need something to do things a certain way, I do so. If I have a problem I can't fix I ask someone that may know more than I do about the given subject. I had exactly the same problem during a recent upgrade. It annoyed me for about a minute after I encountered it until I fixed it. I used neither the internet or a book to fix it, just my own brain. Go figure. I like the Arch way, and as a matter of fact if Arch didn't exist I would probably be using LFS. More work, yes, but my way.
Offline
replacing the any old nanorc with the default shipped and probably installed as /etc/nanorc.pacnew config should solve all issues. nano shouldn't destroy config files anymore. adding one useful configure switch is still enough vanilla. other major distribution do it the same way. it's still easy to rebuild the pkg without that switch if someone wants the line wrapping back.
Offline
replacing the any old nanorc with the default shipped and probably installed as /etc/nanorc.pacnew config should solve all issues. nano shouldn't destroy config files anymore. adding one useful configure switch is still enough vanilla. other major distribution do it the same way. it's still easy to rebuild the pkg without that switch if someone wants the line wrapping back.
Wouldn't it make a little more sense to keep the option enabled, and add "nowrap" to the default nanorc shipped with the package?
Offline
I see that noone read closing message on the bug report I posted, so here it is in plain text:
Closed by Andreas Radke (AndyRTR)
Monday, 25 August 2008, 13:40 GMT+1
Reason for closing: Fixed
Additional comments about closing: I disabled line wrapping in 2.0.8-1 release to prevent such issues for the future.
Of course, that don't solve the problem on the current livecd
Last edited by Mr.Elendig (2008-09-05 13:10:01)
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
This report is still under discussion.
Offline
$ file `which nano`
/usr/bin/nano: symbolic link to `/usr/bin/vim'
$
Not sure what you mean...
Offline
I tried to adapt after using -w for many years with pico and then with nano. But I admin many servers that are not Arch based and instinctively type -w after nano.
So I submitted a package to the AUR that is the same as the official repo package but without the --disable-wrapping flag.
As a temporary measure, this goes a long way.
From what I understand of the dev thread, the --disable-wrapping flag option isn't an "upstream" default. If we want to maintain everything as close to the upstream setup then the best would be to remove the flag at compile-time. To maintain installation integrity, I don't believe that adding a note saying "watch out for the wrapping!" is good enough. I find that laughable at best. The installer should just use the -w flag as its the simplest and least "invasive" way to completely avoid the original problem (wrapping of config and/or script files causing an installation to go awry).
If you want to customise, you can always either add the -w or modify your nanorc. You should already be used to having to do this if you've got nano experience from other distros. This thread just shows that this very small (yet significant) change has only added confusion into the mix.
Maybe we should just submit a bug to nano's devs asking them to change the default behaviour. Then we can confuse every other distro's users instead! hehe.
Last edited by zatricky (2008-10-09 21:30:34)
pacman russian roulette: yes | pacman -Rcs $(pacman -Q | LANG=C sort -R | head -n $((RANDOM % 10)))
(yes, I know its broken)
Offline