Ygthkb

Why write a book when there's a movie in my head?

Is there a way to pause a running process on Linux systems and resume later?

Is it ethical to apply for a job on someone's behalf?

Variance of sine and cosine of a random variable

How can I portray body horror and still be sensitive to people with disabilities?

Why is Bernie Sanders maximum accepted donation on actblue $5600?

How does holding onto an active but un-used credit card affect your ability to get a loan?

For the Circle of Spores druid's Halo of Spores feature, is your reaction used regardless of whether the other creature succeeds on the saving throw?

SQL Server 2017 crashes when backing up because filepath is wrong

If I have Haste cast on me, does it reduce the casting time for my spells that normally take more than a turn to cast?

Euler and minus sign

Are all power cords made equal?

How can guns be countered by melee combat without raw-ability or exceptional explanations?

How can I make my enemies feel real and make combat more engaging?

Is there any danger of my neighbor having my wife's signature?

What does it mean when an external ID field follows a DML Statement?

What does @ mean in a hostname in DNS configuration?

When distributing a Linux kernel driver as source code, what's the difference between Proprietary and GPL license?

Was the Soviet N1 really capable of sending 9.6 GB/s of telemetry?

Custom token in scatter

How bad is a Computer Science course that doesn't teach Design Patterns?

What happens if both players misunderstand the game state until it's too late?

Cryptic cross... with words

Isn't a semicolon (';') needed after a function declaration in C++?

bash aliases do not expand even with shopt expand_aliases

Which of the following shell operations are performed inside the function body when running a function definition and when calling a function?How can I show the results after Bash reads one complete line of input but before executing any of the commands on that line?Why not use alias in compound commands?“a word that is identical to an alias being expanded is not expanded a second time”how to let sudo fork bash instead of sh?man ignoring aliaswhat shell is used to run a scriptDoes a noninteractive login shell execute `~/.profile` or a file whose name is `$BASH_ENV`?bash echo the command line executed at the command line itself (not in a script)Why is an alias in a script being sourced in an interactive bash process not expanded?

2

I want to run an alias inside a bash -c construct.

The bash manual says:

Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt

In this example, why is the alias hi not found when setting expand_aliases explicitly?

% bash -O expand_aliases -c "alias hi='echo hello'; alias; shopt expand_aliases; hi"

alias hi='echo hello'

expand_aliases  on

bash: hi: command not found

I'm running GNU bash, version 5.0.0(1)-release (x86_64-pc-linux-gnu).

Context: I want to be able to run an alias at idle priority, eg a script containing:

#!/bin/bash

exec chrt -i 0 nice -n 19 ionice -c 3 bash -c ". ~/.config/bash/aliases; shopt -s expand_aliases; $(shell-quote "$@")"

I want to avoid using bash -i as I don't want my .bashrc to be read.

bash alias

share|improve this question

edited 47 mins ago

Tom Hale

asked 58 mins ago

Tom HaleTom Hale

7,10833797

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  The paragraph right after the quoted statement from the Bash manual seems to cover this: '...Aliases are expanded when a command is read, not when it is executed. Therefore, an alias definition appearing on the same line as another command does not take effect until the next line of input is read. The commands following the alias definition on that line are not affected by the new alias....'
  
  – Haxiel
  39 mins ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Haxiel, you really should write things like that as answers.
  
  – ilkkachu
  35 mins ago
  

  
  
  
  

add a comment | 

2

I want to run an alias inside a bash -c construct.

The bash manual says:

Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt

In this example, why is the alias hi not found when setting expand_aliases explicitly?

% bash -O expand_aliases -c "alias hi='echo hello'; alias; shopt expand_aliases; hi"

alias hi='echo hello'

expand_aliases  on

bash: hi: command not found

I'm running GNU bash, version 5.0.0(1)-release (x86_64-pc-linux-gnu).

Context: I want to be able to run an alias at idle priority, eg a script containing:

#!/bin/bash

exec chrt -i 0 nice -n 19 ionice -c 3 bash -c ". ~/.config/bash/aliases; shopt -s expand_aliases; $(shell-quote "$@")"

I want to avoid using bash -i as I don't want my .bashrc to be read.

bash alias

share|improve this question

edited 47 mins ago

Tom Hale

asked 58 mins ago

Tom HaleTom Hale

7,10833797

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  The paragraph right after the quoted statement from the Bash manual seems to cover this: '...Aliases are expanded when a command is read, not when it is executed. Therefore, an alias definition appearing on the same line as another command does not take effect until the next line of input is read. The commands following the alias definition on that line are not affected by the new alias....'
  
  – Haxiel
  39 mins ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Haxiel, you really should write things like that as answers.
  
  – ilkkachu
  35 mins ago
  

  
  
  
  

add a comment | 

I want to run an alias inside a bash -c construct.

The bash manual says:

Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt

In this example, why is the alias hi not found when setting expand_aliases explicitly?

% bash -O expand_aliases -c "alias hi='echo hello'; alias; shopt expand_aliases; hi"

alias hi='echo hello'

expand_aliases  on

bash: hi: command not found

I'm running GNU bash, version 5.0.0(1)-release (x86_64-pc-linux-gnu).

Context: I want to be able to run an alias at idle priority, eg a script containing:

#!/bin/bash

exec chrt -i 0 nice -n 19 ionice -c 3 bash -c ". ~/.config/bash/aliases; shopt -s expand_aliases; $(shell-quote "$@")"

I want to avoid using bash -i as I don't want my .bashrc to be read.

bash alias

share|improve this question

edited 47 mins ago

Tom Hale

asked 58 mins ago

Tom HaleTom Hale

7,10833797

% bash -O expand_aliases -c "alias hi='echo hello'; alias; shopt expand_aliases; hi"

alias hi='echo hello'

expand_aliases  on

bash: hi: command not found

#!/bin/bash

exec chrt -i 0 nice -n 19 ionice -c 3 bash -c ". ~/.config/bash/aliases; shopt -s expand_aliases; $(shell-quote "$@")"

share|improve this question

edited 47 mins ago

Tom Hale

asked 58 mins ago

Tom HaleTom Hale

7,10833797

share|improve this question

edited 47 mins ago

Tom Hale

asked 58 mins ago

Tom HaleTom Hale

7,10833797

asked 58 mins ago

Tom HaleTom Hale

7,10833797

asked 58 mins ago

Tom HaleTom Hale

7,10833797

2 Answers
2

active

oldest

votes

5

It doesn't seem work if you set the alias on the same line as it's used. Probably something to do with how aliases are expanded really early in the command line processing, before the actual parsing stage. On an interactive shell:

$ alias foo

bash: alias: foo: not found

$ alias foo='echo foo'; foo         # 2 

bash: foo: command not found

$ alias foo='echo bar'; foo         # 3

foo

$ foo

bar

Note how the alias used is one line late: on the second command it doesn't find the alias just set, and on the third command it uses the one that was previously set.

So, it works if we put a newline within the -c string:

$ bash -c $'shopt -s expand_aliases; alias foo="echo foo";n foo'

foo

(You could also use bash -O expand_aliases -c ... instead of using shopt within the script, not that it helps with the newline.)

Alternatively, you could use a shell function instead of an alias, they're much better in other ways, too:

$ bash -c 'foo() { echo foo; }; foo'

foo

share|improve this answer

answered 46 mins ago

ilkkachuilkkachu

59.6k894168

add a comment | 

0

Turning my comment into an answer, as suggested by ilkkachu.

The Bash manual (linked to in the question) does provide an explanation of how the aliases are handled when there is an alias definition and a command on the same line.

Quote (slightly formatted for clarity):

The rules concerning the definition and use of aliases are somewhat
confusing. Bash always reads at least one complete line of input, and
all lines that make up a compound command, before executing any of the
commands on that line or the compound command.

Aliases are expanded when a command is read, not when it is executed.
Therefore, an alias definition appearing on the same line as another
command does not take effect until the next line of input is read. The
commands following the alias definition on that line are not affected
by the new alias.

This behavior is also an issue when functions are executed. Aliases
are expanded when a function definition is read, not when the function
is executed, because a function definition is itself a command. As a
consequence, aliases defined in a function are not available until
after that function is executed.

To be safe, always put alias definitions on a separate line, and do
not use alias in compound commands.

ilkkachu's answer provides multiple possible solutions to this problem.

share

answered 1 min ago

HaxielHaxiel

2,7851916

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502257%2fbash-aliases-do-not-expand-even-with-shopt-expand-aliases%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

5

It doesn't seem work if you set the alias on the same line as it's used. Probably something to do with how aliases are expanded really early in the command line processing, before the actual parsing stage. On an interactive shell:

$ alias foo

bash: alias: foo: not found

$ alias foo='echo foo'; foo         # 2 

bash: foo: command not found

$ alias foo='echo bar'; foo         # 3

foo

$ foo

bar

Note how the alias used is one line late: on the second command it doesn't find the alias just set, and on the third command it uses the one that was previously set.

So, it works if we put a newline within the -c string:

$ bash -c $'shopt -s expand_aliases; alias foo="echo foo";n foo'

foo

(You could also use bash -O expand_aliases -c ... instead of using shopt within the script, not that it helps with the newline.)

Alternatively, you could use a shell function instead of an alias, they're much better in other ways, too:

$ bash -c 'foo() { echo foo; }; foo'

foo

share|improve this answer

answered 46 mins ago

ilkkachuilkkachu

59.6k894168

add a comment | 

5

It doesn't seem work if you set the alias on the same line as it's used. Probably something to do with how aliases are expanded really early in the command line processing, before the actual parsing stage. On an interactive shell:

$ alias foo

bash: alias: foo: not found

$ alias foo='echo foo'; foo         # 2 

bash: foo: command not found

$ alias foo='echo bar'; foo         # 3

foo

$ foo

bar

Note how the alias used is one line late: on the second command it doesn't find the alias just set, and on the third command it uses the one that was previously set.

So, it works if we put a newline within the -c string:

$ bash -c $'shopt -s expand_aliases; alias foo="echo foo";n foo'

foo

(You could also use bash -O expand_aliases -c ... instead of using shopt within the script, not that it helps with the newline.)

Alternatively, you could use a shell function instead of an alias, they're much better in other ways, too:

$ bash -c 'foo() { echo foo; }; foo'

foo

share|improve this answer

answered 46 mins ago

ilkkachuilkkachu

59.6k894168

add a comment | 

It doesn't seem work if you set the alias on the same line as it's used. Probably something to do with how aliases are expanded really early in the command line processing, before the actual parsing stage. On an interactive shell:

$ alias foo

bash: alias: foo: not found

$ alias foo='echo foo'; foo         # 2 

bash: foo: command not found

$ alias foo='echo bar'; foo         # 3

foo

$ foo

bar

Note how the alias used is one line late: on the second command it doesn't find the alias just set, and on the third command it uses the one that was previously set.

So, it works if we put a newline within the -c string:

$ bash -c $'shopt -s expand_aliases; alias foo="echo foo";n foo'

foo

(You could also use bash -O expand_aliases -c ... instead of using shopt within the script, not that it helps with the newline.)

Alternatively, you could use a shell function instead of an alias, they're much better in other ways, too:

$ bash -c 'foo() { echo foo; }; foo'

foo

share|improve this answer

answered 46 mins ago

ilkkachuilkkachu

59.6k894168

$ alias foo

bash: alias: foo: not found

$ alias foo='echo foo'; foo         # 2 

bash: foo: command not found

$ alias foo='echo bar'; foo         # 3

foo

$ foo

bar

$ bash -c $'shopt -s expand_aliases; alias foo="echo foo";n foo'

foo

$ bash -c 'foo() { echo foo; }; foo'

foo

share|improve this answer

answered 46 mins ago

ilkkachuilkkachu

59.6k894168

answered 46 mins ago

ilkkachuilkkachu

59.6k894168

answered 46 mins ago

ilkkachuilkkachu

59.6k894168

0

Turning my comment into an answer, as suggested by ilkkachu.

The Bash manual (linked to in the question) does provide an explanation of how the aliases are handled when there is an alias definition and a command on the same line.

Quote (slightly formatted for clarity):

The rules concerning the definition and use of aliases are somewhat
confusing. Bash always reads at least one complete line of input, and
all lines that make up a compound command, before executing any of the
commands on that line or the compound command.

Aliases are expanded when a command is read, not when it is executed.
Therefore, an alias definition appearing on the same line as another
command does not take effect until the next line of input is read. The
commands following the alias definition on that line are not affected
by the new alias.

This behavior is also an issue when functions are executed. Aliases
are expanded when a function definition is read, not when the function
is executed, because a function definition is itself a command. As a
consequence, aliases defined in a function are not available until
after that function is executed.

To be safe, always put alias definitions on a separate line, and do
not use alias in compound commands.

ilkkachu's answer provides multiple possible solutions to this problem.

share

answered 1 min ago

HaxielHaxiel

2,7851916

add a comment | 

0

Turning my comment into an answer, as suggested by ilkkachu.

The Bash manual (linked to in the question) does provide an explanation of how the aliases are handled when there is an alias definition and a command on the same line.

Quote (slightly formatted for clarity):

The rules concerning the definition and use of aliases are somewhat
confusing. Bash always reads at least one complete line of input, and
all lines that make up a compound command, before executing any of the
commands on that line or the compound command.

Aliases are expanded when a command is read, not when it is executed.
Therefore, an alias definition appearing on the same line as another
command does not take effect until the next line of input is read. The
commands following the alias definition on that line are not affected
by the new alias.

This behavior is also an issue when functions are executed. Aliases
are expanded when a function definition is read, not when the function
is executed, because a function definition is itself a command. As a
consequence, aliases defined in a function are not available until
after that function is executed.

To be safe, always put alias definitions on a separate line, and do
not use alias in compound commands.

ilkkachu's answer provides multiple possible solutions to this problem.

share

answered 1 min ago

HaxielHaxiel

2,7851916

add a comment | 

Turning my comment into an answer, as suggested by ilkkachu.

The Bash manual (linked to in the question) does provide an explanation of how the aliases are handled when there is an alias definition and a command on the same line.

Quote (slightly formatted for clarity):

The rules concerning the definition and use of aliases are somewhat
confusing. Bash always reads at least one complete line of input, and
all lines that make up a compound command, before executing any of the
commands on that line or the compound command.

Aliases are expanded when a command is read, not when it is executed.
Therefore, an alias definition appearing on the same line as another
command does not take effect until the next line of input is read. The
commands following the alias definition on that line are not affected
by the new alias.

This behavior is also an issue when functions are executed. Aliases
are expanded when a function definition is read, not when the function
is executed, because a function definition is itself a command. As a
consequence, aliases defined in a function are not available until
after that function is executed.

To be safe, always put alias definitions on a separate line, and do
not use alias in compound commands.

ilkkachu's answer provides multiple possible solutions to this problem.

share

answered 1 min ago

HaxielHaxiel

2,7851916

share

answered 1 min ago

HaxielHaxiel

2,7851916

answered 1 min ago

HaxielHaxiel

2,7851916

answered 1 min ago

HaxielHaxiel

2,7851916