On Saturday, September 21, 2024, Koichi Murase
wrote:
>
> Emacs has `auto-mode-alist'. VS Code has `files.associations'.
>
I think he meant a command line option. Like something you can put in FCEDIT
--
Oğuz
> Do these editors have an option that sets the language for syntax
> checking?
I don't know. I usually use Emacs, so I'm only familiar with Emacs.
For Emacs, yes, and I've already submitted a patch to address this
issue to the Emacs mailing list. But clearly, not all editors are
as highly custo
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -flto=auto -ffat-lto-objects
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-secu
2024年9月21日(土) 1:09 Chet Ramey :
> On 9/20/24 2:41 AM, shynur . wrote:
> > `fc` will create a temporary file named something
> > like "bash-fc.Esf9by", which seldom benefits from
> > editors that use *suffixes* to infer what syntax
> > highlighting should be enabled.
>
> Do these editors have an opt
On 9/20/24 2:41 AM, shynur . wrote:
`fc` will create a temporary file named something
like "bash-fc.Esf9by", which seldom benefits from
editors that use *suffixes* to infer what syntax
highlighting should be enabled.
Do these editors have an option that sets the language for syntax checking?
On 9/19/24 1:39 AM, Stephane Chazelas wrote:
Looks like printf(3) gets called with a `Lf' conversation specifier and
a double argument.
Yes, I came to the same conclusion with an essentially identical fix.
[...]
Would it be possible to have a 5.2 patch released with the
backport of those two
In 2024 an editor having such a simplistic approach counts as a bug.
But perhaps adding a variable would allow anyone to nominate their own
favourite, such as as BASHFC_TMPNAM=/tmp/bash-fc.$$.XX.sh
Alternatively, perhaps an extra line could be inserted at the start of the
b file, like « #!fc-
On Fri, Sep 20, 2024 at 12:00 PM shynur . wrote:
> Editors needn't give "bash-fc.NN" special handling, IMO.
A good editor would.
Oğuz:
>
> shynur:
> >
> > Oğuz:
> > >
> > > shynur:
> > > >
> > > > "bash-fc.Esf9by", which seldom benefits from editors
> > > > that use *suffixes* to infer what syntax highlighting
> > > > should be enabled.
> > >
> > > For example?
> >
> > When Emacs opens a file named "bash-fc.NN.bash", it'
On Fri, Sep 20, 2024 at 11:20 AM shynur . wrote:
> - When Emacs opens a file named "bash-fc.NN.bash",
> it'll enable sh-mode automatically
Vim does that without the .bash extension. What stops Emacs from doing the same?
- When Emacs opens a file named "bash-fc.NN.bash",
it'll enable sh-mode automatically, and even start
a LSP server for Bash if configured properly.
- VS Code behaves similarly.
If you've never used a code editor with automatic syntax
highlighting, give them a try.
On Friday, September 20, 2024, shynur . wrote:
>
> editors that use *suffixes* to infer what syntax
> highlighting should be enabled.
>
For example?
--
Oğuz
12 matches
Mail list logo
