[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#17991: shell-mode: fails to recognize .bashrc files as shell scripts

From: Andrew Pennebaker
Subject: bug#17991: shell-mode: fails to recognize .bashrc files as shell scripts
Date: Fri, 11 Jul 2014 07:20:18 -0500

That's not a bad idea.

Personally, I don't like inserting any editor-specific text in my code (I woundn't use the equivalent Vim cookie either).

My current workaround is to manually add (.\bashrc|\.profile).* to auto-mode-alist. I just wish this were the default pattern.

... is there another convention for naming multiple bash configs, per machine, that matches the existing patterns? I guess I could use ".bashrc.android.sh", ugly but functional.

On Jul 11, 2014 2:20 AM, "Kevin Rodgers" <address@hidden> wrote:
On 7/10/14 1:17 PM, Andrew Pennebaker wrote:
Yes, same on my machine.

I think this problem is specific to alternative config files (I've got a
".bashrc" for primary computer, ".bashrc-cygwin" for Windows, ".bashrc-android"
for Android, and so on.

Could the default auto-mode-alist entry be tweaked to include any file with
".bashrc" as a prefix?

Why not just add a major mode cookie (comment) at the top of your
non-standardly-named files?

# -*- mode: sh; -*-

On Thu, Jul 10, 2014 at 1:23 PM, Glenn Morris <address@hidden <mailto:address@hidden>>

    Andrew Pennebaker wrote:

     > Would be helpful if shell-mode understood that .bashrc*, .profile*, etc.
     > are shell scripts. Right now, they are treated as fundamental.

    Works for me.

    emacs-24.3 -Q .profile    -> shell-script
    emacs-24.3 -Q .bashrc     -> shell-script

    C-h v auto-mode-alist
      ("\\.[ck]?sh\\'\\|\\.shar\\'\\|/\\.z?profile\\'" . sh-mode)
      . sh-mode)
      . sh-mode)


Andrew Pennebaker
www.yellosoft.us <http://www.yellosoft.us>

Kevin Rodgers
Denver, Colorado, USA

reply via email to

[Prev in Thread] Current Thread [Next in Thread]