in bash, read after a pipe is not setting values












17















Edit : original title was "read fails in bash"



With ksh I'm using read as a convenient way to separate values: 



$ echo 1 2 3 4 5 | read a b dump

$ echo $b $a 

2 1

$


But it fails in bash :



$ echo 1 2 3 4 5 | read a b dump

$ echo $b $a 



$


I didn't find a reason in the man page why it fails, any idea ?






bash shell pipe read







share|improve this question




















  • 1





    This is discussed (somewhat obscurely) in page 024 of Greg’s Bash FAQ.

    – Scott
    Jul 11 '14 at 18:27
















17















Edit : original title was "read fails in bash"



With ksh I'm using read as a convenient way to separate values: 



$ echo 1 2 3 4 5 | read a b dump

$ echo $b $a 

2 1

$


But it fails in bash :



$ echo 1 2 3 4 5 | read a b dump

$ echo $b $a 



$


I didn't find a reason in the man page why it fails, any idea ?






bash shell pipe read







share|improve this question




















  • 1





    This is discussed (somewhat obscurely) in page 024 of Greg’s Bash FAQ.

    – Scott
    Jul 11 '14 at 18:27














17












17








17


2






Edit : original title was "read fails in bash"



With ksh I'm using read as a convenient way to separate values: 



$ echo 1 2 3 4 5 | read a b dump

$ echo $b $a 

2 1

$


But it fails in bash :



$ echo 1 2 3 4 5 | read a b dump

$ echo $b $a 



$


I didn't find a reason in the man page why it fails, any idea ?






bash shell pipe read







share|improve this question
















Edit : original title was "read fails in bash"



With ksh I'm using read as a convenient way to separate values: 



$ echo 1 2 3 4 5 | read a b dump

$ echo $b $a 

2 1

$


But it fails in bash :



$ echo 1 2 3 4 5 | read a b dump

$ echo $b $a 



$


I didn't find a reason in the man page why it fails, any idea ?






bash shell pipe read




bash shell pipe read






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 21 '18 at 10:52









Gilles

534k12810741594




534k12810741594










asked Jul 11 '14 at 10:34









EmmanuelEmmanuel

3,03411120




3,03411120








  • 1





    This is discussed (somewhat obscurely) in page 024 of Greg’s Bash FAQ.

    – Scott
    Jul 11 '14 at 18:27














  • 1





    This is discussed (somewhat obscurely) in page 024 of Greg’s Bash FAQ.

    – Scott
    Jul 11 '14 at 18:27








1




1





This is discussed (somewhat obscurely) in page 024 of Greg’s Bash FAQ.

– Scott
Jul 11 '14 at 18:27





This is discussed (somewhat obscurely) in page 024 of Greg’s Bash FAQ.

– Scott
Jul 11 '14 at 18:27










2 Answers
2






active

oldest

votes


















22














bash runs the right-hand side of a pipeline in a subshell context, so changes to variables (which is what read does) are not preserved — they die when the subshell does, at the end of the command.



Instead, you can use process substitution:



$ read a b dump < <(echo 1 2 3 4 5)

$ echo $b $a

2 1


In this case, read is running within our primary shell, and our output-producing command runs in the subshell. The <(...) syntax creates a subshell and connects its output to a pipe, which we redirect into the input of read with the ordinary < operation. Because read ran in our main shell the variables are set correctly.



As pointed out in a comment, if your goal is literally to split a string into variables somehow, you can use a here string:



read a b dump <<<"1 2 3 4 5"


I assume there's more to it than that, but this is a better option if there isn't.






share|improve this answer



















  • 3





    Or even read a b dump <<< '1 2 3 4 5'.

    – choroba
    Jul 11 '14 at 10:41











  • Thank you to all, btw I noted that mksh (on cygwin) is doing the same as bash.

    – Emmanuel
    Jul 11 '14 at 10:56











  • @Michael Homer Good explanation! I found another one example that can explain that every command in pipeline run in own subshell: cat /etc/passwd | (read -r line ; echo $line). But next echo of $line which is not in pipeline put nothing on screen, because value was existed just between parentheses (subshell) . Hope, It helps someone.

    – Yurij Goncharuk
    May 3 '18 at 10:28





















14














This is not a bash bug as POSIX allows both bash and ksh behaviors, leading to the unfortunate discrepancy you are observing.



http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_12



Additionally, each command of a multi-command pipeline is in a subshell environment; as an extension, however, any or all commands in a pipeline may be executed in the current environment. All other commands shall be executed in the current shell environment.



However, with bash 4.2 and newer, you can set the lastpipe option in non interactive scripts to get the expected result, eg:



#!/bin/bash



echo 1 2 3 4 5 | read a b dump

echo before: $b $a 

shopt -s lastpipe

echo 1 2 3 4 5 | read a b dump

echo after: $b $a


Output:



before:

after: 2 1





share|improve this answer





















  • 1





    +1 thank you for the "lastpipe" info. sorry for the delay

    – Emmanuel
    Jul 29 '14 at 14:47






  • 1





    the problem with lastpipe is that it doesn't work in other shells (e.g. dash). there's basically no way to do this portable short of running everything in that subshell, see stackoverflow.com/questions/36268479/…

    – anarcat
    Feb 8 '17 at 15:46






  • 1





    @anarcat This is correct but the question asked here was about bash.

    – jlliagre
    Feb 8 '17 at 15:49











  • @anarcat: This may change in the future since there is a wish to change POSIX for another reason (PIPE Status) see here: unix.stackexchange.com/questions/476834/… Changing other shells is not trivial, it took me several months to rewrite the parser and interpeter on the Bourne Shell (bosh) to implement the faster behavior of the modern ksh.

    – schily
    Oct 21 '18 at 13:42













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


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f143958%2fin-bash-read-after-a-pipe-is-not-setting-values%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









22














bash runs the right-hand side of a pipeline in a subshell context, so changes to variables (which is what read does) are not preserved — they die when the subshell does, at the end of the command.



Instead, you can use process substitution:



$ read a b dump < <(echo 1 2 3 4 5)

$ echo $b $a

2 1


In this case, read is running within our primary shell, and our output-producing command runs in the subshell. The <(...) syntax creates a subshell and connects its output to a pipe, which we redirect into the input of read with the ordinary < operation. Because read ran in our main shell the variables are set correctly.



As pointed out in a comment, if your goal is literally to split a string into variables somehow, you can use a here string:



read a b dump <<<"1 2 3 4 5"


I assume there's more to it than that, but this is a better option if there isn't.






share|improve this answer



















  • 3





    Or even read a b dump <<< '1 2 3 4 5'.

    – choroba
    Jul 11 '14 at 10:41











  • Thank you to all, btw I noted that mksh (on cygwin) is doing the same as bash.

    – Emmanuel
    Jul 11 '14 at 10:56











  • @Michael Homer Good explanation! I found another one example that can explain that every command in pipeline run in own subshell: cat /etc/passwd | (read -r line ; echo $line). But next echo of $line which is not in pipeline put nothing on screen, because value was existed just between parentheses (subshell) . Hope, It helps someone.

    – Yurij Goncharuk
    May 3 '18 at 10:28


















22














bash runs the right-hand side of a pipeline in a subshell context, so changes to variables (which is what read does) are not preserved — they die when the subshell does, at the end of the command.



Instead, you can use process substitution:



$ read a b dump < <(echo 1 2 3 4 5)

$ echo $b $a

2 1


In this case, read is running within our primary shell, and our output-producing command runs in the subshell. The <(...) syntax creates a subshell and connects its output to a pipe, which we redirect into the input of read with the ordinary < operation. Because read ran in our main shell the variables are set correctly.



As pointed out in a comment, if your goal is literally to split a string into variables somehow, you can use a here string:



read a b dump <<<"1 2 3 4 5"


I assume there's more to it than that, but this is a better option if there isn't.






share|improve this answer



















  • 3





    Or even read a b dump <<< '1 2 3 4 5'.

    – choroba
    Jul 11 '14 at 10:41











  • Thank you to all, btw I noted that mksh (on cygwin) is doing the same as bash.

    – Emmanuel
    Jul 11 '14 at 10:56











  • @Michael Homer Good explanation! I found another one example that can explain that every command in pipeline run in own subshell: cat /etc/passwd | (read -r line ; echo $line). But next echo of $line which is not in pipeline put nothing on screen, because value was existed just between parentheses (subshell) . Hope, It helps someone.

    – Yurij Goncharuk
    May 3 '18 at 10:28
















22












22








22







bash runs the right-hand side of a pipeline in a subshell context, so changes to variables (which is what read does) are not preserved — they die when the subshell does, at the end of the command.



Instead, you can use process substitution:



$ read a b dump < <(echo 1 2 3 4 5)

$ echo $b $a

2 1


In this case, read is running within our primary shell, and our output-producing command runs in the subshell. The <(...) syntax creates a subshell and connects its output to a pipe, which we redirect into the input of read with the ordinary < operation. Because read ran in our main shell the variables are set correctly.



As pointed out in a comment, if your goal is literally to split a string into variables somehow, you can use a here string:



read a b dump <<<"1 2 3 4 5"


I assume there's more to it than that, but this is a better option if there isn't.






share|improve this answer













bash runs the right-hand side of a pipeline in a subshell context, so changes to variables (which is what read does) are not preserved — they die when the subshell does, at the end of the command.



Instead, you can use process substitution:



$ read a b dump < <(echo 1 2 3 4 5)

$ echo $b $a

2 1


In this case, read is running within our primary shell, and our output-producing command runs in the subshell. The <(...) syntax creates a subshell and connects its output to a pipe, which we redirect into the input of read with the ordinary < operation. Because read ran in our main shell the variables are set correctly.



As pointed out in a comment, if your goal is literally to split a string into variables somehow, you can use a here string:



read a b dump <<<"1 2 3 4 5"


I assume there's more to it than that, but this is a better option if there isn't.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jul 11 '14 at 10:40









Michael HomerMichael Homer

47.3k8124162




47.3k8124162








  • 3





    Or even read a b dump <<< '1 2 3 4 5'.

    – choroba
    Jul 11 '14 at 10:41











  • Thank you to all, btw I noted that mksh (on cygwin) is doing the same as bash.

    – Emmanuel
    Jul 11 '14 at 10:56











  • @Michael Homer Good explanation! I found another one example that can explain that every command in pipeline run in own subshell: cat /etc/passwd | (read -r line ; echo $line). But next echo of $line which is not in pipeline put nothing on screen, because value was existed just between parentheses (subshell) . Hope, It helps someone.

    – Yurij Goncharuk
    May 3 '18 at 10:28
















  • 3





    Or even read a b dump <<< '1 2 3 4 5'.

    – choroba
    Jul 11 '14 at 10:41











  • Thank you to all, btw I noted that mksh (on cygwin) is doing the same as bash.

    – Emmanuel
    Jul 11 '14 at 10:56











  • @Michael Homer Good explanation! I found another one example that can explain that every command in pipeline run in own subshell: cat /etc/passwd | (read -r line ; echo $line). But next echo of $line which is not in pipeline put nothing on screen, because value was existed just between parentheses (subshell) . Hope, It helps someone.

    – Yurij Goncharuk
    May 3 '18 at 10:28










3




3





Or even read a b dump <<< '1 2 3 4 5'.

– choroba
Jul 11 '14 at 10:41





Or even read a b dump <<< '1 2 3 4 5'.

– choroba
Jul 11 '14 at 10:41













Thank you to all, btw I noted that mksh (on cygwin) is doing the same as bash.

– Emmanuel
Jul 11 '14 at 10:56





Thank you to all, btw I noted that mksh (on cygwin) is doing the same as bash.

– Emmanuel
Jul 11 '14 at 10:56













@Michael Homer Good explanation! I found another one example that can explain that every command in pipeline run in own subshell: cat /etc/passwd | (read -r line ; echo $line). But next echo of $line which is not in pipeline put nothing on screen, because value was existed just between parentheses (subshell) . Hope, It helps someone.

– Yurij Goncharuk
May 3 '18 at 10:28







@Michael Homer Good explanation! I found another one example that can explain that every command in pipeline run in own subshell: cat /etc/passwd | (read -r line ; echo $line). But next echo of $line which is not in pipeline put nothing on screen, because value was existed just between parentheses (subshell) . Hope, It helps someone.

– Yurij Goncharuk
May 3 '18 at 10:28















14














This is not a bash bug as POSIX allows both bash and ksh behaviors, leading to the unfortunate discrepancy you are observing.



http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_12



Additionally, each command of a multi-command pipeline is in a subshell environment; as an extension, however, any or all commands in a pipeline may be executed in the current environment. All other commands shall be executed in the current shell environment.



However, with bash 4.2 and newer, you can set the lastpipe option in non interactive scripts to get the expected result, eg:



#!/bin/bash



echo 1 2 3 4 5 | read a b dump

echo before: $b $a 

shopt -s lastpipe

echo 1 2 3 4 5 | read a b dump

echo after: $b $a


Output:



before:

after: 2 1





share|improve this answer





















  • 1





    +1 thank you for the "lastpipe" info. sorry for the delay

    – Emmanuel
    Jul 29 '14 at 14:47






  • 1





    the problem with lastpipe is that it doesn't work in other shells (e.g. dash). there's basically no way to do this portable short of running everything in that subshell, see stackoverflow.com/questions/36268479/…

    – anarcat
    Feb 8 '17 at 15:46






  • 1





    @anarcat This is correct but the question asked here was about bash.

    – jlliagre
    Feb 8 '17 at 15:49











  • @anarcat: This may change in the future since there is a wish to change POSIX for another reason (PIPE Status) see here: unix.stackexchange.com/questions/476834/… Changing other shells is not trivial, it took me several months to rewrite the parser and interpeter on the Bourne Shell (bosh) to implement the faster behavior of the modern ksh.

    – schily
    Oct 21 '18 at 13:42


















14














This is not a bash bug as POSIX allows both bash and ksh behaviors, leading to the unfortunate discrepancy you are observing.



http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_12



Additionally, each command of a multi-command pipeline is in a subshell environment; as an extension, however, any or all commands in a pipeline may be executed in the current environment. All other commands shall be executed in the current shell environment.



However, with bash 4.2 and newer, you can set the lastpipe option in non interactive scripts to get the expected result, eg:



#!/bin/bash



echo 1 2 3 4 5 | read a b dump

echo before: $b $a 

shopt -s lastpipe

echo 1 2 3 4 5 | read a b dump

echo after: $b $a


Output:



before:

after: 2 1





share|improve this answer





















  • 1





    +1 thank you for the "lastpipe" info. sorry for the delay

    – Emmanuel
    Jul 29 '14 at 14:47






  • 1





    the problem with lastpipe is that it doesn't work in other shells (e.g. dash). there's basically no way to do this portable short of running everything in that subshell, see stackoverflow.com/questions/36268479/…

    – anarcat
    Feb 8 '17 at 15:46






  • 1





    @anarcat This is correct but the question asked here was about bash.

    – jlliagre
    Feb 8 '17 at 15:49











  • @anarcat: This may change in the future since there is a wish to change POSIX for another reason (PIPE Status) see here: unix.stackexchange.com/questions/476834/… Changing other shells is not trivial, it took me several months to rewrite the parser and interpeter on the Bourne Shell (bosh) to implement the faster behavior of the modern ksh.

    – schily
    Oct 21 '18 at 13:42
















14












14








14







This is not a bash bug as POSIX allows both bash and ksh behaviors, leading to the unfortunate discrepancy you are observing.



http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_12



Additionally, each command of a multi-command pipeline is in a subshell environment; as an extension, however, any or all commands in a pipeline may be executed in the current environment. All other commands shall be executed in the current shell environment.



However, with bash 4.2 and newer, you can set the lastpipe option in non interactive scripts to get the expected result, eg:



#!/bin/bash



echo 1 2 3 4 5 | read a b dump

echo before: $b $a 

shopt -s lastpipe

echo 1 2 3 4 5 | read a b dump

echo after: $b $a


Output:



before:

after: 2 1





share|improve this answer















This is not a bash bug as POSIX allows both bash and ksh behaviors, leading to the unfortunate discrepancy you are observing.



http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_12



Additionally, each command of a multi-command pipeline is in a subshell environment; as an extension, however, any or all commands in a pipeline may be executed in the current environment. All other commands shall be executed in the current shell environment.



However, with bash 4.2 and newer, you can set the lastpipe option in non interactive scripts to get the expected result, eg:



#!/bin/bash



echo 1 2 3 4 5 | read a b dump

echo before: $b $a 

shopt -s lastpipe

echo 1 2 3 4 5 | read a b dump

echo after: $b $a


Output:



before:

after: 2 1






share|improve this answer














share|improve this answer



share|improve this answer








edited Jul 12 '14 at 9:25

























answered Jul 12 '14 at 9:18









jlliagrejlliagre

46.9k783133




46.9k783133








  • 1





    +1 thank you for the "lastpipe" info. sorry for the delay

    – Emmanuel
    Jul 29 '14 at 14:47






  • 1





    the problem with lastpipe is that it doesn't work in other shells (e.g. dash). there's basically no way to do this portable short of running everything in that subshell, see stackoverflow.com/questions/36268479/…

    – anarcat
    Feb 8 '17 at 15:46






  • 1





    @anarcat This is correct but the question asked here was about bash.

    – jlliagre
    Feb 8 '17 at 15:49











  • @anarcat: This may change in the future since there is a wish to change POSIX for another reason (PIPE Status) see here: unix.stackexchange.com/questions/476834/… Changing other shells is not trivial, it took me several months to rewrite the parser and interpeter on the Bourne Shell (bosh) to implement the faster behavior of the modern ksh.

    – schily
    Oct 21 '18 at 13:42
















  • 1





    +1 thank you for the "lastpipe" info. sorry for the delay

    – Emmanuel
    Jul 29 '14 at 14:47






  • 1





    the problem with lastpipe is that it doesn't work in other shells (e.g. dash). there's basically no way to do this portable short of running everything in that subshell, see stackoverflow.com/questions/36268479/…

    – anarcat
    Feb 8 '17 at 15:46






  • 1





    @anarcat This is correct but the question asked here was about bash.

    – jlliagre
    Feb 8 '17 at 15:49











  • @anarcat: This may change in the future since there is a wish to change POSIX for another reason (PIPE Status) see here: unix.stackexchange.com/questions/476834/… Changing other shells is not trivial, it took me several months to rewrite the parser and interpeter on the Bourne Shell (bosh) to implement the faster behavior of the modern ksh.

    – schily
    Oct 21 '18 at 13:42










1




1





+1 thank you for the "lastpipe" info. sorry for the delay

– Emmanuel
Jul 29 '14 at 14:47





+1 thank you for the "lastpipe" info. sorry for the delay

– Emmanuel
Jul 29 '14 at 14:47




1




1





the problem with lastpipe is that it doesn't work in other shells (e.g. dash). there's basically no way to do this portable short of running everything in that subshell, see stackoverflow.com/questions/36268479/…

– anarcat
Feb 8 '17 at 15:46





the problem with lastpipe is that it doesn't work in other shells (e.g. dash). there's basically no way to do this portable short of running everything in that subshell, see stackoverflow.com/questions/36268479/…

– anarcat
Feb 8 '17 at 15:46




1




1





@anarcat This is correct but the question asked here was about bash.

– jlliagre
Feb 8 '17 at 15:49





@anarcat This is correct but the question asked here was about bash.

– jlliagre
Feb 8 '17 at 15:49













@anarcat: This may change in the future since there is a wish to change POSIX for another reason (PIPE Status) see here: unix.stackexchange.com/questions/476834/… Changing other shells is not trivial, it took me several months to rewrite the parser and interpeter on the Bourne Shell (bosh) to implement the faster behavior of the modern ksh.

– schily
Oct 21 '18 at 13:42







@anarcat: This may change in the future since there is a wish to change POSIX for another reason (PIPE Status) see here: unix.stackexchange.com/questions/476834/… Changing other shells is not trivial, it took me several months to rewrite the parser and interpeter on the Bourne Shell (bosh) to implement the faster behavior of the modern ksh.

– schily
Oct 21 '18 at 13:42




















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f143958%2fin-bash-read-after-a-pipe-is-not-setting-values%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

How to make a Squid Proxy server?

Image
1 I want to set up squid proxy server for monitoring user activity in a network and Internet Web URL filtering for user. I also want to configure the user login, user log, user access group, and block unwanted web sites in my network. Please help me and guide me the full process to do this. server proxy squid share | improve this question edited Jul 31 '12 at 14:45 Jorge Castro 37.1k 107 422 617 asked Jul 31 '12 at 5:16 Goivind Tiwari Goivind Tiwari ...
Read more

Is this a new Fibonacci Identity?

Image
6 1 $begingroup$ I have found the following Fibonacci Identity (and proved it). If $F_n$ denotes the nth Fibonacci Number, we have the following identity begin{equation} F_{n-r+h}F_{n+k+g+1} - F_{n-r+g}F_{n+k+h+1} = (-1)^{n+r+h+1} F_{g-h}F_{k+r+1} end{equation} where $F_1 = F_2 = 1$ , $r leq n$ , $h leq g$ , and $n, g, k in mathbb{N}$ . It is not too hard to show that this identity subsumes Cassini's Identity, Catalan's Identity, Vajda's Idenity, and d'Ocagne's identity to name a few. I have done a pretty thorough literature review, and I have not found anything like this, but I am still wondering if anyone has seen this identity before? I found this by accident after noticing some patterns in some analysis work I was doing, so if this is already known I would be curious to see w...
Read more

19世紀

Image
この記事は検証可能な参考文献や出典が全く示されていないか、不十分です。 出典を追加して記事の信頼性向上にご協力ください。 （ 2012年3月 ） 千年紀: 2千年紀 世紀: 18世紀 - 19世紀 - 20世紀 十年紀: 1800年代 1810年代 1820年代 1830年代 1840年代 1850年代 1860年代 1870年代 1880年代 1890年代 19世紀に君臨した大英帝国。 19世紀 （じゅうきゅうせいき）は、西暦1801年から西暦1900年までの100年間を指す世紀。 目次 1 19世紀の歴史 1.1 国民国家の成立 1.2 帝国主義の興隆 1.3 列強の植民地争奪戦 2 できごと 2.1 1800年代 2.2 1810年代 2.3 1820年代 2.4 1830年代 2.5 1840年代 2.6 1850年代 2.7 1860年代 2.8 1870年代 2.9 1880年代 2.10 1890年代 2.11 1900年代 3 文化 3.1 文学 3.2 音楽 3.3 思想 3.4 科学 3.5 技術 4 人物 4.1 ヨーロッパ 4.1.1 政治家・王族 4.1.1.1 フランス 4.1.1.2 オーストリア＝ハンガリー 4.1.1.3 ロシア 4.1.1.4 イギリス 4.1.1.5 ドイツ（プロイセンほかドイツ領邦を含む） 4.1.1.6 北欧 4.1.1.7 イタリア 4.1.1.8 スペイン 4.1.1.9 ベルギー 4.1.1.10 ギリシア 4.1.2 軍人 4.1.3 実業家 4.1.4 科学と技術 4.1.5 思想と哲学・人文諸学 4.1.6 宗教 4.1.7 文学 4.1.8 美術 4.1.9 音楽 4.1.10 社会事業家 4.1.11 探検家・旅行家 4.1.12 料...
Read more