GNU nano - Bugs: bug #53661, [Request] support for per-syntax...
You are not allowed to post comments on this tracker with your current authentication level.
bug #53661: [Request] support for per-syntax tabbing behavior
Submitter: | Andrew Pennebaker <mcandre> | ||
Submitted: | Sun 15 Apr 2018 04:27:35 PM UTC | ||
Severity: | 1 - Wish | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Jump to the original submission
Sat 05 Oct 2019 09:44:21 AM UTC, comment #11: |
Benno Schulenberg <bens> |
Wed 25 Sep 2019 05:47:13 PM UTC, comment #10: Thanks for reporting back. The feature has been pushed to master, commit 3644d51b. |
Benno Schulenberg <bens> |
Mon 23 Sep 2019 09:40:18 AM UTC, comment #9: Benno - thanks for the new patches (file #47560, file #47561). I've checked out master at commit 4d44b03, applied both patches, then built with "--enable-utf8".
|
Russell Currie <th3f1tz> |
Sun 22 Sep 2019 06:03:00 PM UTC, comment #8: Updated patch and documentation patch are attached. If you have time, please test and then report what you think. |
Benno Schulenberg <bens> |
Mon 07 Jan 2019 10:44:17 AM UTC, comment #7: Benno - thanks for pointing out the tabstospaces/tab behaviour. The "tab" command does achieve what I want it to, and if I am aware of the behaviour, I can work with that. It does strike me that the difference may catch out some users though. "tab" also adds an extra command alongside "tabsize" and "tabstospaces" to achieve something very similar for the end user. Is this making things unnecessarily complex for the end user? - An alternative option may be to let users set "tabsize" and "tabstospaces" in included .nanorc files? (Not sure how much work, or how achievable that is.)
|
Russell Currie <th3f1tz> |
Thu 20 Dec 2018 03:53:51 PM UTC, comment #6: Thanks for testing. Butbe aware that there is a difference between using tabstospaces and the 'tab' command. When using tabstospaces (with the default tabsize of 8), and you type three spaces into an empty buffer and then <Tab>, this <Tab> will add five spaces -- to reach the next "tab stop", so to speak. But when using the 'tab' command followed by a string of eight spaces, typing three spaces into an empty buffer followed by <Tab>, this <Tab> will add eight spaces -- the <Tab> key is no longer aware of "tab stops".
|
Benno Schulenberg <bens> |
Tue 18 Dec 2018 02:32:05 PM UTC, comment #5: Benno - thanks for the quick reply on this one, I hadn't expected one so soon. I'm using the nano 3.2 compiled from source obtained from nano-editor.org (nano-3.2.tar.xz) with your patch applied.
|
Russell Currie <th3f1tz> |
Tue 18 Dec 2018 01:04:51 PM UTC, comment #4: Please see the attached patch, and test whether it achieves all that you want. |
Benno Schulenberg <bens> |
Tue 18 Dec 2018 12:44:01 PM UTC, comment #3: I'd like to chime in and say that this is also something I'm after.
|
Russell Currie <th3f1tz> |
Mon 01 Oct 2018 11:25:18 AM UTC, comment #2: This is exactly what i want.. I can't use nano for my python files right now, because I use it mainly for PHP files on my system, which caused me to set nano to use 4 spaces instead of tabs. |
Henry van Megen <hvanmegen> |
Mon 16 Apr 2018 07:09:28 PM UTC, comment #1: Hmmm... What would be needed is a 'tab' command in the relevant nanorc file, specifying what to do for the <Tab> key -- just like the 'comment' command defines what characters to insert in order to comment a line.
|
Benno Schulenberg <bens> |
Sun 15 Apr 2018 04:27:35 PM UTC, original submission:
Now that many programming languages support conflicting indentation styles (hard tabs for make and Go, soft tabs for F#), it would be helpful if nano supported the ability to adjust style options on a per-programming language basis. nano should be able to “do the right thing” when the Tab keyboard key is pressed. We’re not asking for autoindenting or introspection, just a way to customize nano to insert either a hard tab literal, or else a configurable number of soaces, when the tab key is pressed, soecifically depending on the file ending / minetype / shebang. |
Andrew Pennebaker <mcandre> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 12 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-10-05 | bens | Open/Closed | Open | Closed | |
2019-09-25 | bens | Status | Ready For Test | Fixed | |
2019-09-22 | bens | Attached File | - | Added 0001-new-feature-a-tabgives-command-to-define-what-the-Ta.patch, #47560 | |
Attached File | - | Added 0002-docs-describe-the-new-tabgives-syntax-file-command.patch, #47561 | |||
Status | None | Ready For Test | |||
Assigned to | None | bens | |||
2018-12-31 | bens | Summary | [Request] support per-programming language style defaults | [Request] support for per-syntax tabbing behavior | |
2018-12-18 | bens | Attached File | - | Added 0001-possible-new-feature-a-tab-command-to-define-what-th.patch, #45688 | |
2018-12-18 | th3f1tz | Carbon-Copy | - | Added th3f1tz | |
2018-10-03 | djc | Carbon-Copy | - | Added djc | |
2018-04-17 | bens | Severity | 3 - Normal | 1 - Wish | |
Summary | support per-programming language style defaults | [Request] support per-programming language style defaults |
Powered by Savane 3.13-f8d8.
Corresponding source code
The 'tabgives' command has been released in nano-4.5.