unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: hput <hputn3@zohomail.com>
To: help-gnu-emacs@gnu.org
Subject: (unknown)
Date: Thu, 17 Feb 2022 14:24:06 -0500	[thread overview]
Message-ID: <874k4xqotl.fsf@local.lan> (raw)

When I do scripting in ksh93 emacs defaults to a mode that on the
bar across the bottom where page and char number appear it says:
                  (shell-script[ksh 88] abbrev)

I know very little about ksh 88, and do know that it is considered out
dated.

Is there a mode specifically for ksh93?

It seems that when in that `ksh 88' mode my cursor is continually
jerked to a position that is definitely wrong for where I am in the
script.

Now, when I press <enter> after typing the `fi' in an `if' clause, my
cursur is jerked to the position one would add "content" to an `if'
clause, (the `bleh bleh' ) below.

Example:

if [ $this ];then
   bleh bleh
fi <RET>
   [] <= cusor lands here

Instead of
   
if [ $this ];then
   bleh bleh
fi <RET>
[] <= here, where it needs to be for most next steps

From that position (first `if' clause) cursor needs to go to the far
left edge where one might start more scripting such as another `if'
clause.  And that wrong behavior continues throughout the rest of the
script.

Unlike perl-mode .. where cursor lands where it should.

If the `ksh' script has more than a few lines, that can get
aggravating and time consuming to have to get the cursor to the far
left.  What ever means one uses to position the cursor there is a
pause => action and begin again for more scripting. Why is that?




             reply	other threads:[~2022-02-17 19:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17 19:24 hput [this message]
2022-02-17 20:03 ` (unknown) Stefan Monnier via Users list for the GNU Emacs text editor
  -- strict thread matches above, loose matches on Subject: below --
2024-05-21  2:03 (unknown) Tennyson Bardwell
2023-02-11 20:24 (unknown) cheyrn via Users list for the GNU Emacs text editor
2022-07-09 13:53 (unknown) Lorenzo Isella
2022-07-09 15:06 ` (unknown) Óscar Fuentes
2021-06-06  8:06 (unknown) Sai Karthik
2019-10-18  2:46 (unknown) Justin Barclay
2019-05-02  0:36 (unknown) Budi
2019-05-02  0:40 ` (unknown) Óscar Fuentes
2017-04-07 23:43 Understanding how to specify UTF-8 Will Parsons
2017-04-13  5:09 ` B. T. Raven
2017-04-13  6:37   ` (unknown) Eli Zaretskii
2011-09-17  8:02 (unknown) tester12312
2005-01-16 15:38 (unknown) mayuko_v_v_sutekimax
2003-05-12  7:59 (unknown) Knowledg1
2003-05-01  3:08 (unknown) @Traduire
2003-04-03 22:41 (unknown) Sebastian Tennant
2003-03-14  6:09 (unknown) Waruna Singappuli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874k4xqotl.fsf@local.lan \
    --to=hputn3@zohomail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).