mirror of
https://github.com/abraunegg/onedrive
synced 2024-05-04 06:53:23 +02:00
Various little spelling fixes (check with lintian during Debian packaging) (#2027)
* contrib: remove bash hashbang from completion This file starts with the #! sequence that marks interpreted scripts, but it is a bash completion script that is merely intended to be sourced. * src: spelling error (Attemtping => Attempting) * src: spelling error (reponse => response) * src: spelling error (sucessfully => successfully)
This commit is contained in:
parent
0e0fdacf7c
commit
0ab2955bd7
|
@ -1,5 +1,3 @@
|
|||
#!/bin/bash
|
||||
#
|
||||
# BASH completion code for OneDrive Linux Client
|
||||
# (c) 2019 Norbert Preining
|
||||
# License: GPLv3+ (as with the rest of the OneDrive Linux client project)
|
||||
|
|
|
@ -90,7 +90,7 @@ if [ -n "${ONEDRIVE_AUTHFILES:=""}" ]; then
|
|||
ARGS=(--auth-files ${ONEDRIVE_AUTHFILES} ${ARGS[@]})
|
||||
fi
|
||||
|
||||
# Tell client to utilize provided auth reponse based on environment variable
|
||||
# Tell client to utilize provided auth response based on environment variable
|
||||
if [ -n "${ONEDRIVE_AUTHRESPONSE:=""}" ]; then
|
||||
echo "# We are providing the auth response directly to perform authentication"
|
||||
echo "# Adding --auth-response ARG"
|
||||
|
|
|
@ -1136,7 +1136,7 @@ Options:
|
|||
The authorization URL is written to the `authUrl`, then onedrive waits for the file `responseUrl`
|
||||
to be present, and reads the response from that file.
|
||||
--auth-response ARG
|
||||
Perform authentication not via interactive dialog but via providing the reponse url directly.
|
||||
Perform authentication not via interactive dialog but via providing the response url directly.
|
||||
--check-for-nomount
|
||||
Check for the presence of .nosync in the syncdir root. If found, do not perform sync.
|
||||
--check-for-nosync
|
||||
|
|
|
@ -129,7 +129,7 @@ Repeat these steps for each OneDrive new account that you wish to use.
|
|||
## Configuring the client to use multiple OneDrive accounts / configurations using Docker
|
||||
In some situations it may be desirable to run multiple Docker containers at the same time, each with their own configuration.
|
||||
|
||||
To run the Docker container sucessfully, it needs two unique Docker volumes to operate:
|
||||
To run the Docker container successfully, it needs two unique Docker volumes to operate:
|
||||
* Your configuration Docker volumes
|
||||
* Your data Docker volume
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ The below are known issues with this client:
|
|||
|
||||
**Description:**
|
||||
|
||||
When running the client in standalone mode (`--synchronize`) moving folders that are sucessfully synced around between subsequent standalone syncs causes a deletion & re-upload of data to occur.
|
||||
When running the client in standalone mode (`--synchronize`) moving folders that are successfully synced around between subsequent standalone syncs causes a deletion & re-upload of data to occur.
|
||||
|
||||
**Explanation:**
|
||||
|
||||
|
|
|
@ -5,7 +5,7 @@ Current national clouds that are supported are:
|
|||
* Microsoft Cloud Germany
|
||||
* Azure and Office 365 operated by 21Vianet in China
|
||||
|
||||
In order to sucessfully use these specific Microsoft Azure deployments, the following steps are required:
|
||||
In order to successfully use these specific Microsoft Azure deployments, the following steps are required:
|
||||
1. Register an application with the Microsoft identity platform using the Azure portal
|
||||
2. Configure the new application with the appropriate authentication scopes
|
||||
3. Validate that the authentication / redirect URI is correct for your application registration
|
||||
|
|
|
@ -24,7 +24,7 @@ The authorization URL is written to the \fBauthUrl\fP, then \fBonedrive\fP waits
|
|||
the file \fBresponseUrl\fP to be present, and reads the response from that file.
|
||||
.TP
|
||||
\fB\-\-auth\-response\fP ARG
|
||||
Perform authentication not via interactive dialog but via providing the reponse url directly.
|
||||
Perform authentication not via interactive dialog but via providing the response url directly.
|
||||
.TP
|
||||
\fB\-\-check\-for\-nomount\fP
|
||||
Check for the presence of .nosync in the syncdir root. If found, do not perform sync.
|
||||
|
|
|
@ -326,7 +326,7 @@ final class Config
|
|||
"Perform authentication not via interactive dialog but via files read/writes to these files.",
|
||||
&stringValues["auth_files"],
|
||||
"auth-response",
|
||||
"Perform authentication not via interactive dialog but via providing the reponse url directly.",
|
||||
"Perform authentication not via interactive dialog but via providing the response url directly.",
|
||||
&stringValues["auth_response"],
|
||||
"check-for-nomount",
|
||||
"Check for the presence of .nosync in the syncdir root. If found, do not perform sync.",
|
||||
|
|
|
@ -743,7 +743,7 @@ final class OneDriveApi
|
|||
download(url, saveToPath, fileSize);
|
||||
// Does path exist?
|
||||
if (exists(saveToPath)) {
|
||||
// File was downloaded sucessfully - configure the applicable permissions for the file
|
||||
// File was downloaded successfully - configure the applicable permissions for the file
|
||||
log.vdebug("Setting file permissions for: ", saveToPath);
|
||||
saveToPath.setAttributes(cfg.returnRequiredFilePermisions());
|
||||
}
|
||||
|
|
|
@ -5600,7 +5600,7 @@ final class SyncEngine
|
|||
if (errorMessage["error"]["message"].str == "Access denied. You do not have permission to perform this action or access this resource.") {
|
||||
// Issue #1041 - Unable to delete OneDrive content when permissions prevent deletion
|
||||
try {
|
||||
log.vdebug("Attemtping a reverse delete of all child objects from OneDrive");
|
||||
log.vdebug("Attempting a reverse delete of all child objects from OneDrive");
|
||||
foreach_reverse (Item child; children) {
|
||||
log.vdebug("Delete child item from drive: ", child.driveId);
|
||||
log.vdebug("Delete this child item id: ", child.id);
|
||||
|
@ -5628,7 +5628,7 @@ final class SyncEngine
|
|||
if (errorMessage["error"]["message"].str == "Request was cancelled by event received. If attempting to delete a non-empty folder, it's possible that it's on hold") {
|
||||
// Issue #338 - Unable to delete OneDrive content when OneDrive Business Retention Policy is enabled
|
||||
try {
|
||||
log.vdebug("Attemtping a reverse delete of all child objects from OneDrive");
|
||||
log.vdebug("Attempting a reverse delete of all child objects from OneDrive");
|
||||
foreach_reverse (Item child; children) {
|
||||
log.vdebug("Delete child item from drive: ", child.driveId);
|
||||
log.vdebug("Delete this child item id: ", child.id);
|
||||
|
|
|
@ -141,7 +141,7 @@ bool testNetwork()
|
|||
try {
|
||||
log.vdebug("Attempting to contact online service");
|
||||
http.perform();
|
||||
log.vdebug("Shutting down HTTP engine as sucessfully reached OneDrive Online Service");
|
||||
log.vdebug("Shutting down HTTP engine as successfully reached OneDrive Online Service");
|
||||
http.shutdown();
|
||||
return true;
|
||||
} catch (SocketException e) {
|
||||
|
|
Loading…
Reference in a new issue